You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 850430e
Browse filesBrowse the repository at this point in the historyBrowse files
fix(github): restore core parity for override persistence and the plan.md gate
Core resolves through check-prerequisites --require-tasks --include-tasks,
which persists a SPECIFY_FEATURE_DIRECTORY override into feature.json and
requires plan.md before tasks.md. The vendored resolvers did neither, so a
later run reverted to the previously stored feature and the command ran on
features where core stops.
- Persist the override in all three twins, mirroring core's helpers
(relative value, write only on change)
- Require plan.md, with core's error wording; spec.md stays optional, as
core passes no --require-spec here
- Parity tests per runtime: the two-run override sequence, plan.md
rejection, and spec.md remaining optional
- README: correct the resolution and parity claims
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assisted-by: Claude Code (model: Claude Opus 5, autonomous)
Once installed they live under `.specify/extensions/github/scripts/`. The script is a trimmed twin of core's `check-prerequisites`: it resolves the project root and active feature directory, requires `tasks.md`, and reports the design docs alongside it. It performs none of core's `plan.md`/`spec.md`gating, and it never writes `.specify/feature.json`.
65
+
Once installed they live under `.specify/extensions/github/scripts/`. The script is a trimmed twin of core's `check-prerequisites`: it resolves the project root and active feature directory, requires `plan.md` and `tasks.md`, and reports the design docs alongside them. It matches the invocation the core command makes (`--require-tasks --include-tasks`), so `spec.md`stays optional, and a `SPECIFY_FEATURE_DIRECTORY` override is persisted to `.specify/feature.json` the same way core persists it — a later run without the variable resolves to the same feature.
66
66
67
67
## Migrating from the core `taskstoissues` command
Issue creation is unchanged: the same remote validation, the same deduplication across open and closed issues, the same issue titles, and the same hook contract. Feature resolution differs in one way: this extension does not require `plan.md` (see [Scripts](#scripts)), so it can run on a feature where the core command would stop. This extension does **not** register `speckit.taskstoissues` as an alias, so the two commands coexist without shadowing each other while the core command still exists.
85
+
Behavior is unchanged: the same feature resolution, the same `plan.md`and `tasks.md` prerequisites, the same remote validation, the same deduplication across open and closed issues, the same issue titles, and the same hook contract. This extension does **not** register `speckit.taskstoissues` as an alias, so the two commands coexist without shadowing each other while the core command still exists.
0 commit comments