Micro — Write One Group's Specs

Write all micro specs for one group in a single invocation. Each micro spec is a fully self-contained implementation unit — readable without the master spec — carrying its own objective, the full text of the FRs/ACs it covers, a File Operations table, acceptance criteria, and implementation notes.

Gate: the northstar phase must be accepted, AND the group must have a brainstorm entry (/genesis-brainstorm --boundary micro for G{N}).

Inputs

• .genesis/project-state.md (mode)
• spec.md (required — for the Section 13 plan), northstar.md (required), design.md, brainstorm-log.md
• approvals/master.json (verify northstar accepted)
• The constitution; any existing specs in micro-specs/

Process

1. Parse the group number G{N} (refuse if missing).
2. Read Section 13; extract the group's specs (IDs, titles, dependencies, sizes). Cycle-detect the within-group dependency graph; refuse on a cycle. Verify the group exists in the plan.
3. Create .genesis/features/<feature>/micro-specs/.
4. Write specs sequentially in topological dependency order — write one, validate, save, commit, then the next. No batching, no parallel authoring. For each spec, from micro-spec-template.md:
   • Frontmatter: title, spec-id, group, feature, status, dependencies, covers (FR/AC), deferred, reads, writes.
   • Objective; Requirements Covered (full FR/AC text, not just IDs); Dependencies table; content sections; Acceptance Criteria; File Operations (create/modify/delete, mode-aware); Implementation Notes; commit message + PR description.
   • Self-contained check: an implementer must be able to build from this spec alone — all FRs/ACs in full text, paths specific, ACs objectively verifiable.
   • Size check: >500 lines → warn and auto-split into {G.S.1}/{G.S.2} if reasonable (update the plan); else note and proceed.
   • Validate the frontmatter schema, stamp last_validated, then commit.
5. Coverage verification: every FR and AC assigned to the group is covered by at least one spec; report any uncovered.
6. Produce group simulation scenarios (mandatory) covering functional flows, UI/UX states, integration points, stress scenarios, regression risks.
7. Produce a human testing checklist for hands-on testing after merge.
8. Final commit for plan updates + simulations + checklist.

Output

• .genesis/features/<feature>/micro-specs/{Group.Spec}.md — one self-contained spec per file (e.g. 1.3.md).
• .genesis/features/<feature>/simulations/g{N}-scenarios.md — group simulation scenarios. Feeds the F-pass Simulation stage.
• .genesis/features/<feature>/reviews/g{N}-human-review.md — human testing checklist.
• Possibly updated spec.md (Section 13) if a spec was auto-split.

Mode differences

• Greenfield: technical implementation specs (code files, APIs, components).
• Brownfield: add a per-spec Scope Boundary section and an inherited vs introduced column in File Operations; ACs add "no regressions."
• Lowfield: process-stage specs (command templates, artifact schemas, pipeline behavior); ACs verify the stage command exists, the artifact schema validates, and pipeline behavior is correct.

Next step

Implement each spec in order with /genesis-implement, then run the audits.

Natural language triggers

- "write micro specs for group 1"
- "decompose group 0"
- "micro G2"