speckit.plan

Custom agent imported from GruePro/sdd-oc (.github/agents/speckit.plan.agent.md). Copyright stays with the author.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Pre-Execution Checks

Check for extension hooks (before planning):

• Check if .specify/extensions.yml exists in the project root.
• If it exists, read it and look for entries under the hooks.before_plan key
• If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
• Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
• For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
  • If the hook has no condition field, or it is null/empty, treat the hook as executable
  • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
• For each executable hook, output the following based on its optional flag:
  • Optional hook (optional: true):

    ## Extension Hooks
    
    **Optional Pre-Hook**: {extension}
    Command: `/{command}`
    Description: {description}
    
    Prompt: {prompt}
    To execute: `/{command}`
    

  • Mandatory hook (optional: false):

    ## Extension Hooks
    
    **Automatic Pre-Hook**: {extension}
    Executing: `/{command}`
    EXECUTE_COMMAND: {command}
    
    Wait for the result of the hook command before proceeding to the Outline.
    

• If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Outline

1. Setup: Run .specify/scripts/powershell/setup-plan.ps1 -Json from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, and BOOTSTRAP_ID. BRANCH may appear as legacy context, but the active walkthrough is determined by feature.json. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").

2. Load context: Read FEATURE_SPEC and .specify/memory/constitution.md. If oc-bootstrap-onboarding-sdd.md exists, load the relevant Configure SDD to ... sections for the current scope. Load IMPL_PLAN template (already copied).

For ACP- or gateway-oriented bootstrap work, explicitly identify the operator-facing runtime surfaces the scaffold must name, including spawn, bind, steer, kill, status, and health-check commands, even when the runnable gateway config is deferred.

3. Execute plan workflow: Follow the structure in IMPL_PLAN template to:

• Fill Bootstrap Context (mark unknowns as "NEEDS CLARIFICATION")
• Fill Constitution Check section from constitution
• Evaluate gates (ERROR if violations unjustified)
• Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
• Phase 1: Generate data-model.md as an artifact map, contracts/ as optional command or interface contracts, and quickstart.md as an operator bootstrap walkthrough
• For orchestration-focused scopes, define ACP session surfaces, gateway control-plane assumptions, sub-agent depth/steering expectations, and tool-routing boundaries explicitly in contracts/
• Phase 1: Update agent context by running the agent script
• Re-evaluate Constitution Check post-design

4. Stop and report: Command ends after Phase 2 planning. Report bootstrap id, IMPL_PLAN path, and generated artifacts.

5. Check for extension hooks: After reporting, check if .specify/extensions.yml exists in the project root.

   • If it exists, read it and look for entries under the hooks.after_plan key
   • If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
   • Filter out hooks where enabled is explicitly false. Treat hooks without an enabled field as enabled by default.
   • For each remaining hook, do not attempt to interpret or evaluate hook condition expressions:
     • If the hook has no condition field, or it is null/empty, treat the hook as executable
     • If the hook defines a non-empty condition, skip the hook and leave condition evaluation to the HookExecutor implementation
   • For each executable hook, output the following based on its optional flag:
     • Optional hook (optional: true):

       ## Extension Hooks
       
       **Optional Hook**: {extension}
       Command: `/{command}`
       Description: {description}
       
       Prompt: {prompt}
       To execute: `/{command}`
       

     • Mandatory hook (optional: false):

       ## Extension Hooks
       
       **Automatic Hook**: {extension}
       Executing: `/{command}`
       EXECUTE_COMMAND: {command}
       

   • If no hooks are registered or .specify/extensions.yml does not exist, skip silently

Phases

Phase 0: Outline & Research

1. Extract unknowns from Bootstrap Context above:

   • For each NEEDS CLARIFICATION → research task
   • For each dependency → best practices task
   • For each integration → patterns task

2. Generate and dispatch research agents:

   For each unknown in Bootstrap Context:
     Task: "Research {unknown} for {feature context}"
   For each OpenClaw capability choice:
     Task: "Find best practices for {capability} in {bootstrap domain}"

3. Consolidate findings in research.md using format:

   • Decision: [what was chosen]
   • Rationale: [why chosen]
   • Alternatives considered: [what else evaluated]

Output: research.md with all NEEDS CLARIFICATION resolved

Phase 1: Design & Contracts

Prerequisites: research.md complete

1. Extract bootstrap artifacts from feature spec → data-model.md:

• Artifact name, role, dependencies
• Validation rules from requirements
• Transition or ownership notes if applicable

2. Define interface contracts (if the bootstrap exposes external or operator-facing interfaces) → /contracts/:

• Identify command surfaces, channel bindings, gateway interfaces, ACP spawn/bind/steer expectations, or emitted config expectations
• Document the contract format appropriate for the bootstrap type
• Skip if the current wave is purely internal scaffold refactoring

3. Agent context update:
   • Run .specify/scripts/powershell/update-agent-context.ps1 -AgentType copilot
   • These scripts detect which AI agent is in use
   • Update the appropriate agent-specific context file
   • Add only new technology from current plan
   • Preserve manual additions between markers

Output: data-model.md, /contracts/*, quickstart.md, agent-specific file

Key rules

• Use absolute paths
• ERROR on gate failures or unresolved clarifications