From 196c532d0106a0cb79d6224b44d8e92d000d7c2f Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 25 Jan 2026 18:37:33 +0000 Subject: [PATCH 1/2] feat: Hide substeps and add user feedback requirement for spec_driven_development - Add hidden: true to all 6 steps (constitution, specify, clarify, plan, tasks, implement) - Add "Pause for Feedback" instructions in the job description requiring explicit user approval before proceeding to each next step --- library/jobs/spec_driven_development/job.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/library/jobs/spec_driven_development/job.yml b/library/jobs/spec_driven_development/job.yml index cd442feb..a12626e9 100644 --- a/library/jobs/spec_driven_development/job.yml +++ b/library/jobs/spec_driven_development/job.yml @@ -26,6 +26,12 @@ description: | - Projects where specification quality directly impacts implementation success - Teams wanting to capture design decisions for future reference + **IMPORTANT: Pause for Feedback** + After completing each step, you MUST pause and ask the user for feedback before proceeding + to the next step. Do not automatically continue to the next phase. Wait for explicit user + approval or requested changes before moving forward. This ensures the user maintains control + over the development process and can course-correct at each stage. + changelog: - version: "1.0.0" changes: "Initial version based on GitHub spec-kit workflow" @@ -33,6 +39,7 @@ changelog: steps: - id: constitution name: "Establish Constitution" + hidden: true description: "Creates foundational governance principles and development guidelines for the project. Use when starting a new project or establishing standards." instructions_file: steps/constitution.md inputs: @@ -50,6 +57,7 @@ steps: - id: specify name: "Create Specification" + hidden: true description: "Defines functional requirements as user stories without technology choices. Use when starting to design a new feature." instructions_file: steps/specify.md inputs: @@ -74,6 +82,7 @@ steps: - id: clarify name: "Clarify Specification" + hidden: true description: "Resolves ambiguities and gaps in the specification through structured questioning. Use after specification to ensure completeness." instructions_file: steps/clarify.md inputs: @@ -93,6 +102,7 @@ steps: - id: plan name: "Generate Technical Plan" + hidden: true description: "Creates technical implementation strategy including architecture and technology choices. Use after specification is clarified." instructions_file: steps/plan.md inputs: @@ -124,6 +134,7 @@ steps: - id: tasks name: "Generate Task Breakdown" + hidden: true description: "Converts the implementation plan into actionable, ordered development tasks. Use after plan is validated." instructions_file: steps/tasks.md inputs: @@ -149,6 +160,7 @@ steps: - id: implement name: "Execute Implementation" + hidden: true description: "Generates code and assets by executing the task breakdown. Use when ready to build the feature." instructions_file: steps/implement.md inputs: From 9aeec70dd09c33aeb58c298ba77250db44e71ace Mon Sep 17 00:00:00 2001 From: Noah Horton Date: Mon, 26 Jan 2026 10:04:00 -0700 Subject: [PATCH 2/2] Apply suggestion from @nhorton --- library/jobs/spec_driven_development/job.yml | 6 ------ 1 file changed, 6 deletions(-) diff --git a/library/jobs/spec_driven_development/job.yml b/library/jobs/spec_driven_development/job.yml index a12626e9..0fd25616 100644 --- a/library/jobs/spec_driven_development/job.yml +++ b/library/jobs/spec_driven_development/job.yml @@ -26,12 +26,6 @@ description: | - Projects where specification quality directly impacts implementation success - Teams wanting to capture design decisions for future reference - **IMPORTANT: Pause for Feedback** - After completing each step, you MUST pause and ask the user for feedback before proceeding - to the next step. Do not automatically continue to the next phase. Wait for explicit user - approval or requested changes before moving forward. This ensures the user maintains control - over the development process and can course-correct at each stage. - changelog: - version: "1.0.0" changes: "Initial version based on GitHub spec-kit workflow"