kamehadb: Skill for Claude Code

Implement Task

Before coding

Complete steps 3 (approval and lifecycle) and 4 (decisions) before any source creation or edit, including a new project's bootstrap. Steps 1-2 only gather context.

1. Read AGENTS.md and, when it exists, docs/llm/INDEX.md for conventions and affected wiki pages; a missing wiki must not block work. If AGENTS.md contains Read CONVENTIONS.md before editing., read the root CONVENTIONS.md too. Apply only rules whose scopes match the changed files (most specific wins); route same-scope conflicts through user clarification.
2. If application source exists, call the available Skill entry whose local name is read-codebase-context to trace the relevant code path; understand callers, data flow, and error paths before editing. For a source-less project, read the design, tasks, and delta without creating source, and state that callers and error paths do not exist yet. When the active plan has an ## Impact map, follow read-codebase-context's ## Refresh an impact map (an unusable baseline means tracing from scratch; planned source that does not exist yet uses the source-less map rule). Read current source for every existing file to edit; for a planned new file, follow the approved design and read the source after creating it. The map is navigation, not evidence.
3. Follow the approved plan-feature output when one exists. For a change, read the change files that exist (design.md, tasks.md, delta.md), and read tasks.md's ## Approval Gate before editing application code when it exists; a Bounded or bug-fix change may have only delta.md.
   • A tasks.md proceeds only with Status: approved, which covers design.md, tasks.md, and any delta.md together. If it is missing or pending, stop; plan-feature step 9 asks for and records the approval.
   • A legacy plan or an older tasks.md with a Required gate follows the gate rules in ../using-devkit/references/legacy.md; read it when you meet one.