write-plan

Authors template-compliant implementation plans for docs/plans with validation and queueing.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Raynos/kami-kakushi --skill write-plan-raynos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-plan
Source: https://github.com/Raynos/kami-kakushi/tree/main/.claude/skills/write-plan
Command: npx skills add https://github.com/Raynos/kami-kakushi --skill write-plan-raynos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing implementation plans that pass both automated template gates and human review is error-prone: sections get left empty, citations go stale, and parallel agents collide on shared files. This Skill walks you through scaffolding, judgment checks, and validation so plans land cleanly. ## Core Features & Use Cases - Template Scaffolding: Generates a plan skeleton via verify-plan-template.ts classified as build, process, or ops. - Judgment Guidance: Covers grounding surveys, record citations (FB/ADR/HR), sync ripples, seam ownership, and player-reach proof that regex gates cannot check. - Validation & Queueing: Runs the verifier, fixes errors and warnings, and adds the plan to the human reading queue in the same commit. - Use Case: Before implementing a new game feature, scaffold a build plan, cite the ADR demanding it, declare file ownership against live peer plans, and validate before committing. ## Quick Start Ask the assistant to write a plan for the feature you want to build, describing the outcome in one line.

Frequently Asked Questions about write-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an implementation plan that passes template validation?

Scaffold the plan with verify-plan-template.ts using a build, process, or ops class, fill every section while deleting guidance comments, then run the validator and fix all errors and warnings before committing.

When should I write a plan versus just making the change?

Trivial one-line tweaks need no plan, and decision-oriented diagnosis belongs in brainstorms. Write a plan for anything that changes the game, the workflow tooling, or performs a one-shot operation like a release or reconcile.

Why does the plan gate warn about cited file paths?

The gate warns when cited paths do not exist in the current tree. Read the files you cite during the same session, include commit hashes and a survey date, rather than quoting older docs or memory.

How do I avoid conflicts with other agents editing the same files?

Check docs/plans for live plans and the herdr peers list, then explicitly state which files your plan owns and what it must land before or after. Commit by explicit pathspec since the tree is shared.

What makes a build plan's verification section acceptable?

Verification must name a capture, e2e test, fixture, or live drive proving a player can reach the feature. Unit tests alone can pass while the feature remains unreachable in the actual game.