Produce structured spec.md from brainstorm conversations. Creates a consistent format that feeds cleanly into the planning phase.
View on GitHubskills/exploration-write-spec/SKILL.md
February 2, 2026
Select agents to install to:
npx add-skill https://github.com/thebrownproject/space-agents/blob/main/skills/exploration-write-spec/SKILL.md -a claude-code --skill exploration-write-specInstallation paths:
.claude/skills/exploration-write-spec/# /exploration-write-spec - Spec Document Generator Transform brainstorm conversations into structured spec documents. This skill produces consistent `spec.md` files that the planning phase can reliably parse. ## When to Use Called at the end of `/brainstorm` when the user confirms they're ready to capture their exploration. Can also be invoked directly if you have a clear idea ready to document. ## The Process 1. **Gather context** - Review the brainstorm conversation (or get user input if invoked directly) 2. **Extract key elements** - Problem, solution, requirements, constraints 3. **Identify gaps** - Note any open questions that would block planning 4. **Write spec.md** - Use the template below 5. **Confirm output location** - Show user the file path ## Output **Location:** `.space-agents/exploration/ideas/YYYY-MM-DD-<topic>/spec.md` The spec file lives alongside any exploration notes in the same topic folder. This folder will later move to `planned/` when `/plan` processes it. ## spec.md Template ```markdown # Exploration: [Topic Title] **Date:** YYYY-MM-DD **Status:** [Ready for planning | Needs discussion | Blocked] --- ## Problem What problem are we solving? Why does this matter? [1-3 paragraphs describing the problem, its impact, and why it needs solving] --- ## Solution High-level approach. The "what" not the "how". [Describe the solution at a conceptual level. Include diagrams/tables if they clarify the approach.] --- ## Requirements Must-have functionality. Use checklist format for tracking. - [ ] Requirement 1 - [ ] Requirement 2 - [ ] Requirement 3 --- ## Non-Requirements Explicitly out of scope. Prevents scope creep during planning. - Not doing X - Not changing Y - Not supporting Z --- ## Architecture Components, data flow, key technical decisions. [Include diagrams, flow descriptions, component interactions. This section should give a developer enough context to understand how the pieces fit together.] --- ## Constrai