Generates sequential spec file from /dream-team:plan brainstorming. Creates dated .md with linear tasks, conditional design/Playwright flags, cleanup for deterministic single-session execution.
From dream-teamnpx claudepluginhub ratler/dream-team --plugin dream-teamThis skill uses the workspace's default tool permissions.
Convert the brainstorming conversation into a formal spec file for sequential execution — single session, no sub-agents, tasks run one at a time.
Prerequisites: This skill assumes /dream-team:plan has already been run in this session. If the conversation has no brainstorming context (no discussed requirements, no confirmed approach, no validated task breakdown), stop and tell the user: "No brainstorming context found. Run /dream-team:plan <prompt> first to explore requirements and design."
All spec files MUST be named with a date prefix: specs/YYYY-MM-DD-<descriptive-kebab-case>.md
Use today's date. Example: specs/2026-02-07-user-auth-api.md
${CLAUDE_PLUGIN_ROOT}/templates/spec-template.md.mode: sequential and spec-version: 1.playwright: true if the brainstorming decided to use Playwright MCP, otherwise playwright: false.frontend-design: true if the brainstorming discussed frontend/UI work and design direction, otherwise frontend-design: false.frontend-design: true, fill in the ## Design Direction section with the aesthetic style, stack, component libraries, and design notes from the brainstorming conversation. Auto-suggest component libraries based on the chosen stack if not explicitly discussed.## Cleanup section with any teardown commands needed (stop servers, remove temp files). Use "N/A" if nothing to clean up.specs/YYYY-MM-DD-<descriptive-kebab-case>.md using today's date.Specs are executed by agents that have no access to the brainstorming conversation. Every detail left unspecified becomes a coin flip — different builds will make different choices. The goal is deterministic builds: two agents reading the same spec should produce near-identical output.
When writing task descriptions, prefer concrete values over descriptive language:
background: #1a1a2e not "dark background". Write font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif not "system sans-serif stack"."Unable to load weather data" not "an error message". Write "${score} points by ${author} | ${comments} comments" not "display the score, author, and comments".<div>, <p>, <span>), class names, and nesting. Write createElement("div") not "create an element".windspeed_10m with mph or km/h explicitly — don't leave the unit unspecified.classList.remove() or className =.If you catch yourself writing a vague adjective ("red-tinted", "subtle", "clean"), replace it with the exact value. Vague descriptions are the #1 source of build divergence.
Assigned To, Agent Type, Background, or Parallel fields**Files** field listing exactly which files it creates or modifies, prefixed with creates: or modifies:. Review and validation tasks may omit this field.After saving the spec file, commit it:
git add specs/<spec-file>.md
git commit -m "spec: <short description of what the spec covers>"
After saving and committing the spec, output:
Spec written (sequential mode)
File: specs/YYYY-MM-DD-<name>.md
Tasks: <number of tasks>
Complexity: <simple | medium | complex>
Execute with: /dream-team:build specs/YYYY-MM-DD-<name>.md
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.