exploration-write-spec

Generate a structured spec.md from brainstorm conversations for planning workflows.

3|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/thebrownproject/space-agents --skill exploration-write-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exploration-write-spec
Source: https://github.com/thebrownproject/space-agents/tree/main/skills/exploration-write-spec
Command: npx skills add https://github.com/thebrownproject/space-agents --skill exploration-write-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm conversations are frequently informal and difficult to convert into actionable planning artifacts. This skill standardizes these conversations into a consistent spec.md template that can be dropped into the planning workflow.

Core Features & Use Cases

  • Convert brainstorming notes into a ready-to-use spec.md.
  • Output location follows the template path .space-agents/exploration/ideas/YYYY-MM-DD-<topic>/spec.md for easy retrieval.
  • Supports subsequent planning steps by capturing problem, solution, requirements, constraints, and open questions.

Quick Start

Summarize the current brainstorm and generate the spec.md at the specified path using the standardized template.

Frequently Asked Questions about exploration-write-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert brainstorming notes into a structured spec for planning?

To convert brainstorming notes into a structured spec, you need a standardized template that extracts the problem, solution, requirements, constraints, open questions, and outputs, generating a spec.md file ready for the planning phase.

What is the best way to standardize informal brainstorm conversations for software planning?

Standardizing informal brainstorm conversations involves applying a consistent spec.md template to capture problem definitions, solutions, and constraints, ensuring the output is structured and referenced alongside exploration notes for planning.

How do I generate a spec.md from brainstorm sessions using a template?

You generate a spec.md by summarizing the brainstorm conversation and applying a standard template to extract requirements, constraints, and open questions, storing the result under a structured exploration ideas directory path.

Where should I store spec files generated from exploration and brainstorming workflows?

Generated spec files should be stored under the .space-agents/exploration/ideas/YYYY-MM-DD-<topic>/spec.md directory path to ensure easy retrieval and integration with subsequent planning workflows.

What sections should be included in a spec template for software planning?

A spec template for software planning should include dedicated sections for the problem, solution, requirements, constraints, open questions, and outputs to fully capture the brainstorm results for the planning phase.

Can I use a standardized spec template for small brainstorm sessions?

Yes, you can use a standardized spec template for small brainstorm sessions because it standardizes problem, solution, and requirements extraction, ensuring even informal conversations produce actionable planning artifacts.