plan-with-specslisted

# Plan with Specs ## Skill Info Part of the **spec-manager** agent. This skill generates detailed, actionable implementation plans from finalized specifications. ## Input The user provides a task slug (or task title) as arguments: $ARGUMENTS If no arguments are provided: 1. List all `*/specs.md` files in `specs/` directory 2. Ask the user which one to generate a plan for If a task title (not slug) is provided, convert it to a slug to find the matching files. ## Process ### Step 1: Read All Spec Documents 1. Read `specs/{slug}/requirements.md` - for original context and goals 2. Read `specs/{slug}/specs.md` - for technical specifications 3. If either file doesn't exist or specs status is still "Pending", inform the user and suggest running the appropriate prior step ### Step 2: Validate Specs Readiness Check that specs are sufficiently detailed for planning: - Status is not "Pending" - Technical specifications are defined - Architecture section is filled in - No critical open questions remain If specs have unresolved open questions, warn the user and ask whether to proceed or resolve them first. ### Step 3: Analyze Codebase Before generating the plan: 1. **Examine** the existing codebase structure (project layout, frameworks, patterns) 2. **Identify** existing files that need modification 3. **Find** reusable components, utilities, or patterns 4. **Check** test structure and conventions 5. **Review** configuration and build setup ### Step 4: Generate Implementat