菜单
Stress-test a plan against the project's CONTEXT.md glossary and docs/adr/ decisions by grilling the user one question at a time, surfacing contradictions between user claims and the actual code, and updating CONTEXT.md/ADRs lazily as terms resolve.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | doc-align |
| description | Stress-test a plan against the project's CONTEXT.md glossary and docs/adr/ decisions by grilling the user one question at a time, surfacing contradictions between user claims and the actual code, and updating CONTEXT.md/ADRs lazily as terms resolve. |
doc-align is the grilling discipline of Octopus. It treats
CONTEXT.md as the glossary of record and docs/adr/ as the ledger
of decisions, then walks the user through the decision tree of a plan
one question at a time. Drift in terminology gets recorded inline;
real architectural trade-offs get an ADR — but only if the triple
gate holds.
Engage when the user wants to:
Do not engage for greenfield brainstorming with no existing docs — use
superpowers:brainstorming first, then come back here.
An ADR is proposed only when all three hold:
Missing any one cancels the ADR. Most decisions fail the gate and stay
as code + commit message. Do not paper docs/adr/ with preferences.
Read CONTEXT.md (or CONTEXT-MAP.md for multi-context repos). If
absent, offer to bootstrap a glossary stub before grilling — grilling
without a glossary surfaces drift but has nowhere to record it.
Ask one question at a time. Each question targets one of: a term not in CONTEXT.md, a term used differently from CONTEXT.md, a claim the code might contradict, or a decision treated as obvious when the trade-off is real. The user's answers reshape the tree — never batch.
When the user's claim diverges from what the code actually says, stop and surface the contradiction before the next question. Continuing a chain on a false premise poisons the rest of the session.
CONTEXT.md is glossary only: term → one-sentence definition in the project's voice. No implementation details, no spec content, no scratchpad notes. Cross-references between terms are allowed; long prose is not. Edit inline as terms resolve, never in a batch at the end.
Triple gate passes → draft via /octopus:doc-adr with the decision,
rejected alternatives, and the why. Gate fails → resolution lives in
the commit message or PR description.
doc-prd — synthesises the aligned plan into a tracker PRDrefactor-deepen — uses doc-align for its grilling sub-loopdoc-lifecycle — owns the ADR / Spec / RFC artifacts produced
or consultedsuperpowers:brainstorming — runs before doc-align when
the plan does not yet existRun one high-stakes decision through a council of 5 ephemeral advisor lenses that answer in parallel, peer-review each other anonymously, and get synthesised into a single verdict — agreements, clashes, blind spots, a recommendation, and the one thing to do first. Adapted from Karpathy's LLM Council. For genuine decisions with stakes and tradeoffs, not factual lookups or creation tasks.
PR-time dual-delta read of coverage/complexity/module-size/dependency-cycles vs. orphan-ref baseline; ratchet+absolute thresholds; LLM curation only on breach.
Shrink a SKILL.md without changing meaning — deterministic cleanup first, LLM rewrite only if the target isn't met. Test-file anchors preserved; frontmatter, headings, and code blocks never modified. Dry-run by default; --apply writes.
Capture insights, test hypotheses, and promote confirmed patterns to rules (adapted for multi-agent environments). Default mode is single- developer/session capture to knowledge/. Team mode aggregates recurring review feedback across the fleet into rule-promotion candidates — fleet-wide patterns promote to shared workspace rules, single-repo patterns stay local.
Create, update, and validate the team's Definition of Done (docs/definition- of-done.md). create/update scaffolds from a template and grills the manager for team items; validate walks a diff/PR against the checklist (met/unmet/not-applicable). Signal-only contract referencing existing enforcement (architect, security, audit-*, guardrails) — never gates a commit. Consumed by codereview.
Proactive cadence summary over a knowledge root — 'what changed / what needs you today' without being asked. Deterministic core (octopus briefing, over the octopus kr registry) computes the change-delta since a per-root watermark and composes octopus hygiene + synthesize; this skill narrates it, grounded to source nodes, on the cheapest tier.