Prompt file imported from B0yZ4kr14/OrthoPlus-Enterprise (.github/prompts/speckit.conduct.run.prompt.md). Copyright stays with the author.

speckit.conduct.run

Description

Instructions

name: speckit-conduct-run description: Executes a single spec-kit phase by delegating its steps to specialized sub-agents sequentially and summarizing the outcome. compatibility: Requires spec-kit project structure with .specify/ directory metadata: author: github-spec-kit source: conduct:commands/conduct.md

<user_input_format> The user will trigger you using the following format: /speckit.conduct.run [phase] [optional additional context]

Example: If the user types: /speckit.conduct.run specify I want to create a pomodoro app

1. The [phase] is specify.
2. Run one of the following command to resolve the installed phase instruction file for the active coding tool.

• Bash: .specify/extensions/conduct/scripts/bash/load.sh specify
• Powershell: .specify/extensions/conduct/scripts/powershell/load.ps1 specify

3. The original user input is "I want to create a pomodoro app". </user_input_format>

1. Input Parsing & Information Gathering:

   • Extract the [phase] and the original user input from the user's prompt.
   • Determine the current project root path.
   • Run one of the following commands from the project root.
     • Bash: .specify/extensions/conduct/scripts/bash/load.sh [phase]
     • Powershell: .specify/extensions/conduct/scripts/powershell/load.ps1 [phase]
   • Parse the loader JSON output and capture resolved_path, agent, and framework.
   • Use your available read-only tools to read the contents of resolved_path to understand the rules, checklists, and step-by-step instructions for that phase.

2. Explicit Planning: - Parse the phase instruction file into distinct, numbered steps (e.g., Step 1, Step 2).

3. Logical Decomposition: - Determine the required order of operations. Ensure taking an action does not prevent a subsequent necessary action.

4. Execution via Sequential Delegation: - You must strictly delegate one single step of the phase to a sub-agent at a time. Never group multiple steps together in a single sub-agent delegation. For example, if there are 3 steps, they must be executed by 3 different sub-agents separately and sequentially.

   • When triggering a sub-agent, your prompt to it MUST be formatted clearly and include:
     • Original User Input: The exact contextual string the user provided.
     • Project Root Path: The current workspace/project root path.
     • Step Instructions: Extract the EXACT, verbatim text for that single step directly from the phase file. You must include all original code blocks, bash examples, script paths, and notes exactly as they appear. Do NOT summarize or paraphrase technical instructions.
     • Execution Directive: Explicitly instruct the sub-agent: "Strictly execute the exact scripts and commands provided in the instructions above. Do not invent complex custom scripts or alternative commands if a specific example is provided."
     • Accumulated Context: The results and context gathered from any previously completed steps.
   • Wait for the sub-agent to complete its single step and review its output against the constraints before triggering the next sub-agent for the next step.

5. Outcome Evaluation & File Tracking: - If an observation requires changes to your plan, actively generate new hypotheses and adapt your sub-agent delegation.

   • Continuously track the file paths of any documents, code files, or configuration files generated or modified by your sub-agents during their execution.
   • Prepare to read file contents: After all steps complete, before generating the final summary, use your read-only tools to open and review each tracked file so you can extract and present meaningful content details (requirements, user stories, architecture decisions, tasks, etc.) to the user.

6. Final Summary Generation:

   • Once all steps in your plan are completed (or if the process is halted due to a blocker), read each generated/modified file to extract its actual content.
   • Review the accumulated context and the files tracked in Step 5.
   • Generate a final, easy-to-read summary for the user following the exact format defined in the <output_format> section.
   • Content-rich summaries: The summary must include specific details from each file (user stories, requirements, design decisions, tasks, principles) — not generic descriptions.

<output_format> You have two specific output requirements:

1. Initial Output: Before invoking any sub-agents, output your step-by-step logical plan to the user formatted as a Markdown outline.

2. Final Output: After all sub-agents have completed their steps (or if the workflow is blocked), you MUST output a summary using Markdown sections and emojis. Your summary must strictly follow this template:

🏁 Phase Execution Summary

[Provide a brief, easy-to-read overview of what was successfully accomplished across all steps.]

📄 Generated Files Summary

For each file created, modified, or updated during the phase, you must read the file and extract key content. Provide a bulleted list where each entry includes:

• File path
• Content overview specific to the file type:
  • spec.md: List user stories (if present), key functional requirements, success criteria, data entities, and edge cases
  • plan.md: Summarize the architecture/design approach, which files will be created/modified, and the primary implementation strategy
  • tasks.md: Highlight the task breakdown, dependencies, and estimated scope
  • Constitution: List the core principles and decision-making rules established
  • Other files: Provide a meaningful 2-3 sentence summary of actual content and purpose

Example for spec.md:

• /specs/001-pomodoro-app/spec.md
  • User stories: P1 — start a 25-min work session and 5-min break with countdown timers and end-of-session notifications; P2 — view total sessions completed and total focus time filterable by today/week/all-time, and customise work/break durations that persist across restarts; P3 — pause/resume a session mid-countdown with 30-min auto-expiry, and receive audible + visual notifications when sessions end
  • Functional requirements: start pomodoro with 25-min default; start break with 5-min default; display MM:SS countdown; fire notification on timer completion; persist session history as JSON; show total sessions and focus time; allow custom durations via settings; save settings across restarts; pause and resume active session; enforce single active session at a time; clear transient session state on restart; compute statistics from completed sessions only
  • Success criteria: countdown appears within 2 s of start; timer accurate within ±1 s over 25 min; notifications fire within 2 s of completion; stats visible immediately after any completed session; completed sessions survive app restart; custom durations applied on first use after change; 95 % of start→complete→stats workflows finish without error; all interactions respond in under 500 ms
  • Entities: Session (type, duration, start_time, end_time, status, pause_duration); Statistics (date, sessions_completed, total_focus_time, sessions_by_type); Settings (work_duration, break_duration, notification_type)
  • Edge cases: data loss vs. persistence when app closes mid-session; system clock changes (DST, manual adjustment); invalid duration inputs (zero, negative, extreme values); concurrent session prevention; statistics accuracy for sessions paused for extended periods

Example for plan.md:

• /plans/001-pomodoro-app/plan.md
  • Architecture: CLI application running on Node.js with local JSON file persistence; no external API dependencies
  • Files to create: src/timer.js (countdown engine with pause/resume logic), src/session.js (session lifecycle and persistence), src/stats.js (aggregation queries over session history), src/settings.js (load/save user preferences), src/notify.js (terminal bell + status-line notifications), src/cli.js (interactive command loop and display), data/sessions.json (session store), data/settings.json (user preferences store)
  • Implementation strategy: build and unit-test the timer engine first, wire session persistence next, add statistics and settings layers, then integrate the CLI interface and notifications last

⚠️ Action Required (Incomplete Parts)

[Explicitly list any steps that failed, were skipped, or require the user's manual intervention. If none, state "None".]

⏭️ Next Steps

[Specify the next spec-kit phase or exact commands the user should run next based on the completed work.] </output_format>

Context

• Project: OrthoPlus Enterprise
• Auto-generated from: .kimi/skills/speckit-conduct-run/SKILL.md
• Synced: 2026-05-24T21:37:04-03:00