[codex] add discovery bundled extension#23
Conversation
e00653d to
65073ec
Compare
65073ec to
131df94
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 131df94da4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - Evidence gaps: unsupported claims, missing repository facts, or unresolved constraints. | ||
| - Validation needed: benchmarks, experiments, PoCs, or follow-up discovery required to close decision risk. | ||
|
|
||
| 4. Create or update `feasibility.md` by rendering `templates/feasibility.md`. Prefer the active feature directory when it exists. Otherwise create it under `discovery/<short-name>/feasibility.md`. This command is responsible for input normalization, evidence classification, decision classification, and template field population only. |
There was a problem hiding this comment.
Each discovery command is registered through the command registrar, which rewrites bare top-level templates/ references to .specify/templates/; however these new template files are installed under .specify/extensions/discovery/templates/. In projects using /speckit.discovery.feasibility (and the same pattern in the other discovery commands), the generated agent instruction therefore points at a non-existent template path, so the command cannot reliably render the intended bundled template.
Useful? React with 👍 / 👎.
…xtension # Conflicts: # .github/workflows/community-smoke.yml # tests/integrations/community_defaults.py # tests/test_presets.py
1 participant
Description
Adds the
discoveryextension as a bundled/default Spec Kit extension in this fork.This PR:
extensions/discoveryfrombigsmartben/spec-kit-discoveryat version0.2.0discoveryextensions/discoveryin the CLI wheel package assetsdiscoveryduringspecify initalongside the other fork defaultsThe extension provides 6
/speckit.discovery.*commands for feasibility, technology selection, scenario-specific technical decisions, legacy codebase assessment, API implementation understanding, and proof-of-concept validation.Testing
uv run specify --helpuv sync && uv run pytestAdditional validation performed:
ExtensionManifestvalidation forextensions/discovery/extension.ymluv run pytest tests/integrations/test_cli.py -k "community_extensions_and_workflow_preset_auto_installed or no_git_keeps_community_defaults" -quv run pytest tests/test_arch_templates.py tests/test_presets.py -k "community_smoke_checks_wheel_assets_and_extension_dev_reinstall or init_next_steps_do_not_list_arch_as_core_workflow" -quv build --wheel, then inspected the wheel forspecify_cli/core_pack/extensions/discovery/*specify init,specify extension remove discovery --force, andspecify extension add discoverygit diff --checkAI Disclosure
Used Codex to inspect the extension integration path, copy and wire the bundled extension, update tests/workflow coverage, run validation, prepare this PR, and update the bundled discovery extension to v0.2.0 before merge.