codexspec 0.3.2__tar.gz → 0.3.3__tar.gz

{codexspec-0.3.2 → codexspec-0.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codexspec
-Version: 0.3.2
+Version: 0.3.3
 Summary: CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code
 Project-URL: Homepage, https://github.com/Zts0hg/codexspec
 Project-URL: Repository, https://github.com/Zts0hg/codexspec

{codexspec-0.3.2 → codexspec-0.3.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "codexspec"
-version = "0.3.2"
+version = "0.3.3"
 description = "CodexSpec - A Spec-Driven Development (SDD) toolkit for Claude Code"
 readme = "README.md"
 requires-python = ">=3.11"

{codexspec-0.3.2 → codexspec-0.3.3}/templates/commands/generate-spec.md

@@ -104,3 +104,10 @@ Save the specification to: `.codexspec/specs/{NNN}-{feature-name}/spec.md`
 
 > [!IMPORTANT]
 > This command should be called after `/codexspec.specify` has clarified all requirements. It focuses on document generation, not requirement exploration.
+
+## Available Follow-up Commands
+
+After generating the specification, the user may consider:
+- `/codexspec.review-spec` - to validate the specification quality before technical planning
+- `/codexspec.clarify` - to address any ambiguities or gaps identified
+- `/codexspec.spec-to-plan` - to proceed directly with technical implementation planning

{codexspec-0.3.2 → codexspec-0.3.3}/templates/commands/plan-to-tasks.md

@@ -268,3 +268,9 @@ Phase 5: ┌───────────────┴──────
 - [ ] File paths are specific and accurate
 - [ ] Complexity estimates are reasonable
 - [ ] Checkpoints are defined at phase boundaries
+
+## Available Follow-up Commands
+
+After generating the task breakdown, the user may consider:
+- `/codexspec.review-tasks` - to validate the task breakdown quality before implementation
+- `/codexspec.implement-tasks` - to proceed directly with implementing the tasks

{codexspec-0.3.2 → codexspec-0.3.3}/templates/commands/review-plan.md

@@ -232,8 +232,15 @@ Review the technical implementation plan for quality and readiness. This command
 ## Available Follow-up Commands
 
 Based on the review result, the user may consider:
-- **Pass**: `/codexspec.plan-to-tasks` - to generate task breakdown
-- **Needs Work**: Fix the identified issues, then re-run this review command
+
+### If Issues Found (Warnings or Suggestions)
+- **Direct Fix**: Simply describe the changes you want to make (e.g., "Fix PLAN-001 and add the missing API endpoints") and I will update the plan accordingly
+- **Re-run Review**: `/codexspec.review-plan` - to verify changes after fixing issues
+- **Proceed Anyway**: If you decide the warnings/suggestions are not critical or out of scope for the current iteration, you can proceed directly to `/codexspec.plan-to-tasks`
+
+### Next Steps Based on Review Result
+- **Pass**: `/codexspec.plan-to-tasks` - to proceed with task breakdown
+- **Needs Work**: Fix the identified issues first, then re-run `/codexspec.review-plan` to verify, or proceed anyway if issues are acceptable
 - **Fail**: `/codexspec.spec-to-plan` - to regenerate the technical plan
 ```
 

{codexspec-0.3.2 → codexspec-0.3.3}/templates/commands/review-spec.md

@@ -172,8 +172,15 @@ Review the feature specification for quality and readiness. This command ensures
 ## Available Follow-up Commands
 
 Based on the review result, the user may consider:
-- **Pass**: `/codexspec.spec-to-plan` - to generate technical implementation plan
-- **Needs Work**: `/codexspec.clarify` - to address ambiguities and gaps, then re-run this review
+
+### If Issues Found (Warnings or Suggestions)
+- **Direct Fix**: Simply describe the changes you want to make (e.g., "Fix SPEC-001 and update the acceptance criteria") and I will update the specification accordingly
+- **Re-run Review**: `/codexspec.review-spec` - to verify changes after fixing issues
+- **Proceed Anyway**: If you decide the warnings/suggestions are not critical or out of scope for the current iteration, you can proceed directly to `/codexspec.spec-to-plan`
+
+### Next Steps Based on Review Result
+- **Pass**: `/codexspec.spec-to-plan` - to proceed with technical implementation planning
+- **Needs Work**: Fix the identified issues first, then re-run `/codexspec.review-spec` to verify, or proceed anyway if issues are acceptable
 - **Fail**: `/codexspec.clarify` - to systematically identify and fix specification issues
 ```
 

{codexspec-0.3.2 → codexspec-0.3.3}/templates/commands/review-tasks.md

@@ -281,8 +281,15 @@ Phase 5: [5.1 || 5.2 || 5.3] (parallel)
 ## Available Follow-up Commands
 
 Based on the review result, the user may consider:
+
+### If Issues Found (Warnings or Suggestions)
+- **Direct Fix**: Simply describe the changes you want to make (e.g., "Fix TASK-001 and split Task 2.5 into smaller tasks") and I will update the tasks accordingly
+- **Re-run Review**: `/codexspec.review-tasks` - to verify changes after fixing issues
+- **Proceed Anyway**: If you decide the warnings/suggestions are not critical or out of scope for the current iteration, you can proceed directly to `/codexspec.implement-tasks`
+
+### Next Steps Based on Review Result
 - **Pass**: `/codexspec.implement-tasks` - to begin implementation
-- **Needs Work**: Fix the identified issues, then re-run this review command
+- **Needs Work**: Fix the identified issues first, then re-run `/codexspec.review-tasks` to verify, or proceed anyway if issues are acceptable
 - **Fail**: `/codexspec.plan-to-tasks` - to regenerate the task breakdown
 ```
 

{codexspec-0.3.2 → codexspec-0.3.3}/templates/commands/spec-to-plan.md

@@ -281,3 +281,9 @@ Before saving, verify:
 
 > [!TIP]
 > If the specification path is not provided, look for `spec.md` files in `.codexspec/specs/` and ask the user which one to use.
+
+## Available Follow-up Commands
+
+After generating the technical plan, the user may consider:
+- `/codexspec.review-plan` - to validate the plan quality before task breakdown
+- `/codexspec.plan-to-tasks` - to proceed directly with breaking down into actionable tasks