spec-intakelisted

Transcribe a requirements source into an authoritative spec of record with per-requirement source locators and a field inventory. Accepts a single file, a directory of files, or a completed /interview-me brief; attempts inline conversion using whatever the machine has, and reports what it could not convert. Routing splits on where the requirements live — if they are in a document, use this. Trigger this when someone says: I have a requirements document, the business sent me a spec, turn this document into requirements, intake this document, capture these requirements into a spec, extract the requirements from this file, I was handed a requirements folder. Do NOT use when the requirements are only in someone's head — use /interview-me first. Do NOT use to judge whether the requirements are any good — this transcribes and inventories, it does not review.
chuckplayer/claude-agent-pack · ★ 6 · Data & Documents · score 76

Install: claude install-skill chuckplayer/claude-agent-pack

# Spec Intake Stage 0 of the delivery pipeline. Turn a requirements source into **one authoritative artifact** — a spec of record, hand-editable, with a field inventory as Appendix A inside it — plus a run manifest recording what this run actually saw. The spec of record is the single source of truth. Anything later derived from it is **regenerated from it, never hand-edited**, so a derived view cannot drift from its source. ## 1. Resolve the target, the output path, and the run state **Target.** One of: - **File path(s)** supplied by the user — use them directly. - **A directory** — go to step 2 and survey it before transforming anything. - **An `/interview-me` brief** (`docs/*-brief.md`, recognised by its `## Design Brief` heading) — already markdown, so no conversion is needed. Treat it as an ingested source. - **Nothing supplied** → ask. Never guess a target. **Output path.** Resolve `spec_dir` from the `- **Spec directory:**` key in `docs/CONVENTIONS.md`, defaulting to `docs/specs` when the key is absent. An unfilled `[e.g., ...]` placeholder value counts as unset. Then guard the value, and do it as an action rather than as a principle: **open `agents/tech-lead.md` now and apply its plan-directory rejection table to the resolved `spec_dir`.** Apply **only** that table — **not** that file's Naming section, whose `-2` / `-3` collision suffixes are wrong here for the reason step 1's run-state table gives below. **Do not reproduce the table's rows in this file**: a