Write Sequential Spec

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."

Filename Format

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

What To Do

1. Read the spec template at ${CLAUDE_PLUGIN_ROOT}/templates/spec-template.md.
2. Summarize the agreed plan from the conversation — confirm with the user before writing.
3. Write the spec, filling in all base sections from the brainstorming context.
4. Set frontmatter mode: sequential and spec-version: 1.
5. Set frontmatter playwright: true if the brainstorming decided to use Playwright MCP, otherwise playwright: false.
6. Set frontmatter frontend-design: true if the brainstorming discussed frontend/UI work and design direction, otherwise frontend-design: false.
7. If 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.
8. Tasks must be strictly linear — each depends on the previous one.
9. Do NOT include Team Members, Team Configuration, Review Policy, or agent assignment fields.
10. Fill in the ## Cleanup section with any teardown commands needed (stop servers, remove temp files). Use "N/A" if nothing to clean up.
11. Save to specs/YYYY-MM-DD-<descriptive-kebab-case>.md using today's date.

Eliminating Ambiguity

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:

• CSS: Specify exact hex colors, font stacks, spacing values, border-radius. Write background: #1a1a2e not "dark background". Write font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif not "system sans-serif stack".
• Strings: Write exact user-facing text in quotes. Write "Unable to load weather data" not "an error message". Write "${score} points by ${author} | ${comments} comments" not "display the score, author, and comments".
• DOM structure: Specify element types (<div>, <p>, <span>), class names, and nesting. Write createElement("div") not "create an element".
• API details: Specify exact URLs, query parameters, response field paths, units, and data transformations (rounding, formatting). Write windspeed_10m with mph or km/h explicitly — don't leave the unit unspecified.
• Implementation patterns: When a specific approach matters for consistency, spell it out. For example, specify whether a Promise should reject-and-catch or resolve-with-fallback. Specify timeout values. Specify whether to use classList.remove() or className =.
• Quote style: If the project has a convention, state it (e.g., "use double quotes throughout JS").

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.

Task Rules

• Every task depends on the previous task (task 2 depends on task 1, task 3 depends on task 2, etc.)
• No Assigned To, Agent Type, Background, or Parallel fields
• Each task has: Task ID, Depends On, Description with specific action items, Files, and Tests
• The Tests field lists test file paths and test cases the task must produce. Use "N/A" only for tasks with zero testable code (research, docs, config-only).
• Every builder task must include a **Files** field listing exactly which files it creates or modifies, prefixed with creates: or modifies:. Review and validation tasks may omit this field.
• Start with foundational work, end with a validation task
• Keep tasks small — each should take 2-10 minutes to implement
• Each builder task should produce 1-3 files and ~100-300 lines of code. If a task would be larger, split it into smaller tasks with clear file boundaries.
• The second-to-last task MUST be a code review task — re-read all changed files, check for bugs, missing edge cases, security issues, and style. Fix anything found before final validation.

Git

After saving the spec file, commit it:

git add specs/<spec-file>.md
git commit -m "spec: <short description of what the spec covers>"

Report

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