Using Devkit

Choose the owning workflow skill and follow its instructions. Read context first: read-codebase-context, or setup-codebase on a first visit.

Shared rules

• Name a new process artifact YYYY-MM-DD-<issue-id>-<slug> (before any type suffix) only when the task or a related artifact, including its filename, gives an issue ID; never infer one or rename an artifact.
• Link internally with relative Markdown links; convert legacy [[...]] links in any document you edit and report unresolvable targets.
• Never put process artifacts in or link them from docs/llm/.
• Commit/push only on explicit request, after a final review-and-verify pass. One branch/PR per task; no locks or coordination tools. For conflicts in docs/agent-devkit/INDEX.md or docs/llm/INDEX.md, preserve every task link and verify targets.
• Working-tree changes are user-owned: "clean up" never authorizes git reset --hard, git clean, git stash, or deletes, even after a backup. Ask first.