Plan Requirements

This is the first step in the specification pipeline. Creates a requirements document based on the task context and project. The user provides a spec name and task description, and this command gathers context, asks targeted clarifying questions, and generates a structured requirements document.

When to use

Use this skill when the user needs to:

• Create a new feature specification
• Document requirements for a task
• Generate a structured requirements document for planning

Instructions

Step 1: Gather Information

Project context (optional): Before gathering information, check if .projects/ exists. If it does, scan for a specs.md that references the current spec name. If found:

1. Read the project's vision.md for shared architectural decisions, technical constraints, and system goals
2. Read the relevant spec entry from specs.md for pre-defined purpose, boundary, and dependencies
3. Present this context to the user as a starting point — "This spec is part of project X. Here's the pre-defined context: [purpose, boundary, dependencies, shared decisions]. I'll use this as a starting point."