メニュー
Manages the Skill Knowledge Graph + central index. TRIGGER: a skill's purpose/trigger/phase changes. NOT FOR: minor wording tweaks; first-time creation (use skill-author + authoring-standards).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Enforces format rules + Pre-Creation Protocol for Skill, Sub-agent, Rule files. TRIGGER: create any of them. NOT FOR: WHETHER to create (use skill-author), registration (use skill-graph-manager).
Governs WAL fragment writes (domain/api/rules/data/architecture) at Archive. TRIGGER: STANDARD Archive, dimensions elected via h-archive. NOT FOR: PATCH; wiki authoring (use documentation-curator).
Runs one-round adversarial critique. TRIGGER: HIGH-risk STANDARD — Explorer (Cat A), Propose/Review (Cat B/C). NOT FOR: code review (use code-reviewer); PATCH; >1 round per category.
Orchestrate the repo-aligned AI engineering pipeline (plan → decisions → eval → improve → cleanup → verify → archive) with explicit approval gates. TRIGGER when user asks to run the full pipeline or go from idea to delivery; DO NOT TRIGGER for small tasks or when user invokes a specific phase.
Decides whether to author a SKILL.md. TRIGGER: 'create a skill', recurring workflow without one, broken trigger. NOT FOR: one-offs, rules, non-skill artifacts (use authoring-standards).
Skill navigator. List active skills, locate archived ones, choose the right sequence per scenario.
| name | skill-graph-manager |
| description | Manages the Skill Knowledge Graph + central index. TRIGGER: a skill's purpose/trigger/phase changes. NOT FOR: minor wording tweaks; first-time creation (use skill-author + authoring-standards). |
Focus: bidirectional linking, skill indexing, and consistent cross-skill navigation.
This skill acts as the automated librarian for the workspace. It ensures that all skills are interconnected in a Knowledge Graph, allowing the LLM to naturally associate related skills (e.g., jumping from devops-task-planning to prd-task-splitter automatically).
Action: Read the new or modified SKILL.md. Understand its boundaries, focus, and target audience.
Action: Consult the central index (skill-index/SKILL.md). Identify 2-5 existing skills that are logically related (e.g., predecessor, successor, sibling, or standard constraints).
Action: STOP AND ASK. Use the AskUserQuestion tool or text response to present the proposed links to the user.
Example Prompt: "I've detected a change to skill
X. To maintain the Knowledge Graph, I propose adding bidirectional links betweenXand[Y, Z]. Options:
- Approve all proposed links.
- Add/Remove specific links (please specify).
- Skip graph update this time."
Action: Once the user approves:
## Related Skills section at the bottom of the new/modified SKILL.md.## Related Skills section of the related existing skills.skill-index/SKILL.md to reflect the new graph topology.Whenever you write a bidirectional link inside a SKILL.md, you MUST use this exact Markdown format:
## Related Skills
- [<related-skill-1>](../<related-skill-1>/SKILL.md): <Brief explanation of why they are related, e.g., "The predecessor skill for requirements">
- [<related-skill-2>](../<related-skill-2>/SKILL.md): <Brief explanation, e.g., "Provides the coding standards required by this skill">
skill-author Step 7 delegates "register in central index + maintain bidirectional links" to this skill.authoring-standards hands off registration to this skill.