← ClaudeAtlas

draftinglisted

Use when a mindpowers spec exists and the user wants the actual deliverable written, such as "draft it", "write the memo from the spec", or right after mindstorming locks a spec. Not for code; not for drafting without a spec (offer mindstorming first).
rohitgehe05/mindpowers · ★ 3 · AI & Automation · score 71
Install: claude install-skill rohitgehe05/mindpowers
# Drafting ## Overview The second step in the mindpowers loop: shape (mindstorming) -> draft (drafting) -> review (reviewing-docs) -> remember (calibrating). Mindstorming turns a rough idea into a locked spec. Drafting turns that locked spec into the finished document, holding it to the standards baked into the matched template. Drafting does not re-litigate the spec. The thinking already happened. This skill's job is faithful, high-quality execution: realize every section, honor every exclusion, apply the template's hard requirements, and flag any deviation instead of silently making one. ## Input Contract This skill needs a spec with `status: locked` from `docs/mindpowers/specs/`. 1. **Find the spec.** Use the one the user names, or the most recent spec in `docs/mindpowers/specs/` if the request is ambiguous (e.g. "draft it" right after a mindstorming session). Also check legacy `docs/brainstorm/` if it exists and nothing newer is in `docs/mindpowers/specs/`. 2. **Status is `draft`.** Do not draft from it. Tell the user the spec isn't locked yet, and ask whether to lock it now or go back to mindstorming to finish shaping it. 3. **Status is `superseded`.** Warn the user this spec was superseded (and by what, if the frontmatter or a newer spec says so). Confirm they still want to draft from it before proceeding. 4. **No spec exists for the ask.** Do not draft cold. Give one short pitch for running mindstorming first, something like "I don't see a spec for this. Mindstor