write-speclisted

# Write Spec — Requirements Specification Writer This skill researches a GitHub issue in depth and writes a detailed requirements specification directly into the issue body. ## Step 0: Parse Arguments The issue number must be provided as an argument. If not provided, ask the user for the issue number and stop. ``` ISSUE_NUMBER=<provided argument> REPO="nick-pape/grackle" ``` ## Step 1: Read the Issue ```bash gh issue view $ISSUE_NUMBER -R $REPO ``` Capture the title, body, labels, and any referenced issues (parent epics, related issues, sibling tickets). ## Step 2: Read Related Issues For every issue referenced in the body (parent epics, sibling sub-tasks, related features), read them: ```bash gh issue view <RELATED_NUMBER> -R $REPO ``` This provides context on how this issue fits into the larger feature. ## Step 3: Read Relevant Specs and RFCs Check these spec files in the repo for relevant sections: - `specs/2026-03-18-agent-kernel.md` — Agent Kernel Architecture RFC (task lifecycle, process model, scheduling, IPC, signals) - `specs/2026-03-11-grackle-deep-dive.md` — Full architecture deep dive (all subsystems) - `specs/2026-02-20-v0.md` — Original design spec (UI mockups, interaction patterns) - `specs/2026-03-13-default-personas.md` — Persona roster definitions - `specs/2026-03-12-ux-audit.md` — UX audit findings and recommendations Read the files that are relevant based on the issue's domain (server, web, CLI, powerline, etc.). Use the issue labels to guid