メニュー
This skill should be used when the user wants to define the requirements of a feature or project. Produces numbered requirements and validation criteria. Triggers include "write a spec for", "define the requirements", "what should this do", "capture the requirements".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when checking whether field-guide reference pages still match current code and tests. Reads pages plus fg-evidence anchors, reports or fixes semantic drift, and can use sub-agents for parallel audit batches. Triggers include "resolve drift", "semantic drift", "check accuracy", "verify the reference against code", and "audit the wiki".
Use after ingesting or editing field-guide pages to attach living code/test anchors. Adds or refreshes fg-evidence metadata without trying to prove prose accuracy. Triggers include "update evidence", "wire evidence", "add evidence anchors", and "connect the wiki to code".
Use when extracting knowledge from .lore/ artifacts into the reference wiki. Converts work artifacts (retros, specs, plans, research, notes) into structured wiki pages grouped by knowledge type. Reads Markdown or HTML sources and writes Markdown by default. Triggers include "ingest this", "extract knowledge from", "add this to the wiki", "update the reference from", and "populate the field guide".
Use when setting up field-guide on a project for the first time, or to refresh the scheduled lint job after it expires. Triggers include "init field-guide", "set up field-guide", "refresh field-guide lint schedule", and "bootstrap the wiki".
This skill is used when the project wiki needs a health check. Triggers include 'lint the wiki', 'check wiki health', 'run field-guide lint', 'are there stale wiki pages', 'find orphaned pages', 'check for contradictions in the wiki'.
Use when asking questions about the project wiki, querying accumulated knowledge, searching project decisions or lessons. Triggers include "query the wiki", "what does the wiki say about", "search project knowledge", and natural language questions directed at the field-guide wiki.
| name | specify |
| description | This skill should be used when the user wants to define the requirements of a feature or project. Produces numbered requirements and validation criteria. Triggers include "write a spec for", "define the requirements", "what should this do", "capture the requirements". |
Define what to build and how to know it's done. Requirements, numbered. Validation, explicit. Not how to build it — that's the plan.
Search for related prior work: invoke the lore-researcher agent via Task tool with the topic description — wait for the result. Review any relevant lore context. Ask clarifying questions. Draft. Save. Then run a fresh-eyes review.
After saving, invoke the spec-reviewer agent via Task tool on the saved spec. Present findings and offer to address issues before moving on.
Number requirements with a namespaced prefix to avoid collisions across specs: REQ-{PREFIX}-N
Derive the prefix from the spec filename — take the first 1-2 segments of the kebab-case name, uppercase. auth-flow.md → REQ-AUTH-FLOW. checkout.md → REQ-CHECKOUT. Override with a req-prefix frontmatter field when the auto-generated prefix is awkward or shorter IDs are preferred.
Every spec needs an AI Validation section. It answers: how will the AI verify this is done? It must be behavioral and actionable — something the AI can run or observe. When in doubt, invoke /define-validation to work through it.
Save to .lore/work/specs/[feature-name].md using kebab-case. Load ${CLAUDE_PLUGIN_ROOT}/shared/frontmatter-schema.md for the frontmatter fields. The document body is freeform — what matters is that requirements are numbered and validation is explicit.
Write the body Markdown-first per the "Body Format" section of ${CLAUDE_PLUGIN_ROOT}/shared/frontmatter-schema.md. Reach for embedded inline HTML only where scannability needs it — per-requirement status badges and anchor links per requirement ID so cross-references work.
