prototype

Based on wshobson/agents full-stack-feature (MIT License)

Prototype — Feature Orchestrator

CRITICAL BEHAVIORAL RULES

You MUST follow these rules exactly. Violating any of them is a failure.

1. Execute steps in order. Do NOT skip ahead, reorder, or merge steps.
2. Write output files. Each step MUST produce its output file in .prototype/ before the next step begins. Read from prior step files -- do NOT rely on context window memory.
3. Stop at checkpoints. When you reach a PHASE CHECKPOINT, you MUST stop and wait for explicit user approval before continuing. Use the AskUserQuestion tool with clear options.
4. Halt on failure. If any step fails (agent error, test failure, missing dependency), STOP immediately. Present the error and ask the user how to proceed. Do NOT silently continue.
5. Use only local agents. All subagent_type references use agents bundled with this plugin or general-purpose. No cross-plugin dependencies.
6. Never enter plan mode autonomously. Do NOT use EnterPlanMode. This command IS the plan -- execute it.

Pre-flight Checks

Before starting, perform these checks:

1. Check for existing session

Check if .prototype/state.json exists:

• If it exists and status is "in_progress": Read it, display the current step, and ask the user:

  Found an in-progress prototype session:
  Feature: [name from state]
  Current step: [step from state]
  
  1. Resume from where we left off
  2. Start fresh (archives existing session)
  

  Resuming: Read current_step from state.json. Skip directly to that step — all prior step output files already exist in .prototype/ and should be read from disk, not regenerated.

  Archiving: Move the entire .prototype/ directory to .prototype-archived-{ISO_DATE}/, then create a fresh .prototype/.

• If it exists and status is "complete": Ask whether to archive and start fresh.

2. Initialize state

Create .prototype/ directory and state.json: