codexspec 0.7.0__tar.gz → 0.7.2__tar.gz

{codexspec-0.7.0 → codexspec-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.7.0
+Version: 0.7.2
 Summary: CodexSpec - A Requirements-First SDD toolkit for Claude Code
 Project-URL: Homepage, https://github.com/Zts0hg/codexspec
 Project-URL: Repository, https://github.com/Zts0hg/codexspec

{codexspec-0.7.0 → codexspec-0.7.2}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codexspec"
-version = "0.7.0"
+version = "0.7.2"
 description = "CodexSpec - A Requirements-First SDD toolkit for Claude Code"
 readme = "README.md"
 requires-python = ">=3.11"

{codexspec-0.7.0 → codexspec-0.7.2}/templates/commands/generate-spec.md

@@ -95,6 +95,17 @@ Invoke `/codexspec:review-spec <feature-dir>/spec.md` after saving.
 - Run a maximum of two automatic fix-and-review rounds.
 - If defects remain, the same defect repeats, or remediation requires a user decision, stop and report the evidence.
 
+## Auto-Next Chain Advance
+
+Read `workflow.auto_next` from `.codexspec/config.yml` (default `false`; only the literal value `true` enables it — absent, `false`, or any other value means disabled).
+
+When `workflow.auto_next` is `true` AND the Automatic Review Loop above concluded in a passing state — the final Overall Status is `PASS` or `PASS_WITH_WARNINGS` — advance the chain automatically:
+
+1. Emit exactly one notice line, in the interaction language, e.g. `auto_next: review passed → invoking /codexspec:spec-to-plan <feature-dir>`.
+2. Invoke `/codexspec:spec-to-plan <feature-dir>` exactly once, then end this command.
+
+Do not auto-advance when `workflow.auto_next` is disabled, or the review loop stopped at `NEEDS_REVISION` or `BLOCKED`, or stopped early per the conditions above; in those cases hand control back to the user exactly as the review loop already does. This advances the chain and does not modify the Output Summary.
+
 ## Output Summary
 
 Report:

{codexspec-0.7.0 → codexspec-0.7.2}/templates/commands/plan-to-tasks.md

@@ -92,6 +92,27 @@ Invoke `/codexspec:review-tasks <feature-dir>/tasks.md`.
 - Run a maximum of two automatic fix-and-review rounds.
 - Stop if defects repeat, remain unresolved, or require a user or architecture decision.
 
+## Automatic Cross-Artifact Analysis
+
+When the review loop above concludes in a passing state — the final `/codexspec:review-tasks` Overall Status is `PASS` or `PASS_WITH_WARNINGS` — invoke `/codexspec:analyze <feature-dir>` exactly once.
+
+- Do not invoke analyze when the review loop stopped at `NEEDS_REVISION` or `BLOCKED`, or stopped early per the conditions above; in those cases end here, handing control back to the user as the review loop already does.
+- analyze runs once and is read-only. Present its output as-is; do not auto-fix its findings and do not run a fix-and-reanalyze loop.
+- If `requirements.md` is absent, analyze still runs and discloses its legacy limitation (it starts at `spec.md` and cannot verify fidelity to the original discussion) per its own behavior.
+- analyze's results are informational only. They do not change whether tasks are ready for implementation and do not add a gate before `/codexspec:implement-tasks`.
+- Do not modify the Output Summary for analyze, and do not save an additional analyze report file; analyze's own output is the report.
+
+## Auto-Next Chain Advance
+
+Read `workflow.auto_next` from `.codexspec/config.yml` (default `false`; only the literal value `true` enables it).
+
+When `workflow.auto_next` is `true` AND the review loop above concluded in a passing state (`PASS` or `PASS_WITH_WARNINGS`) — after the analyze step above has run — advance the chain automatically:
+
+1. Emit exactly one notice line, in the interaction language, e.g. `auto_next: review passed → invoking /codexspec:implement-tasks <feature-dir>`.
+2. Invoke `/codexspec:implement-tasks <feature-dir>` exactly once, with no confirmation prompt, then end this command.
+
+analyze's findings are informational only and do NOT block this advance (see the Automatic Cross-Artifact Analysis section above). Do not auto-advance when `workflow.auto_next` is disabled, or the review loop stopped at `NEEDS_REVISION` or `BLOCKED`, or stopped early; hand control back to the user as the review loop already does. This advances the chain and does not modify the Output Summary.
+
 ## Output Summary
 
 Report the tasks path, plan/requirement coverage, dependency summary, unresolved items, and auto-review status.

{codexspec-0.7.0 → codexspec-0.7.2}/templates/commands/spec-to-plan.md

@@ -101,6 +101,17 @@ Invoke `/codexspec:review-plan <feature-dir>/plan.md`.
 - Run a maximum of two automatic fix-and-review rounds.
 - Stop if a defect repeats, remains unresolved, or requires a user decision.
 
+## Auto-Next Chain Advance
+
+Read `workflow.auto_next` from `.codexspec/config.yml` (default `false`; only the literal value `true` enables it — absent, `false`, or any other value means disabled).
+
+When `workflow.auto_next` is `true` AND the Automatic Review Loop above concluded in a passing state — the final Overall Status is `PASS` or `PASS_WITH_WARNINGS` — advance the chain automatically:
+
+1. Emit exactly one notice line, in the interaction language, e.g. `auto_next: review passed → invoking /codexspec:plan-to-tasks <feature-dir>`.
+2. Invoke `/codexspec:plan-to-tasks <feature-dir>` exactly once, then end this command.
+
+Do not auto-advance when `workflow.auto_next` is disabled, or the review loop stopped at `NEEDS_REVISION` or `BLOCKED`, or stopped early per the conditions above; in those cases hand control back to the user exactly as the review loop already does. This advances the chain and does not modify the Output Summary.
+
 ## Output Summary
 
 Report the plan path, requirement coverage, plan-level decisions, unresolved items, and auto-review status.

{codexspec-0.7.0 → codexspec-0.7.2}/templates/commands/specify.md

@@ -107,3 +107,14 @@ Report:
 - Confirmed IDs
 - Open IDs and whether they block specification generation
 - Next command: `/codexspec:generate-spec <feature-dir>`
+
+## Auto-Next Chain Advance
+
+Read `workflow.auto_next` from `.codexspec/config.yml` (default `false`; only the literal value `true` enables it).
+
+When `workflow.auto_next` is `true` AND discovery is complete — the Completion criteria above are met and the user has explicitly confirmed the final stage summary (not each intermediate topic confirmation) — advance the chain automatically:
+
+1. Emit exactly one notice line, in the interaction language, e.g. `auto_next: requirements confirmed → invoking /codexspec:generate-spec <feature-dir>`.
+2. Invoke `/codexspec:generate-spec <feature-dir>` exactly once, then end this command.
+
+Do not auto-advance on intermediate topic confirmations, or when `workflow.auto_next` is disabled (absent, `false`, or non-`true`); in those cases report normally and hand off to the next command manually. This advances the chain and does not modify the Completion report.