thedixitjain Using development-skills
Skip this router for a bounded subagent task. Read the development loop. Resume an active plan at its recorded step; otherwise choose:
Direct applies only when the result, forced solution, and proof are clear. The change must be reversible and carry no business or design choice. Weighing more than one viable approach is a design choice.
Full applies to everything else. Inspect first, run brainstorming, and agree on the result and proof.
Use create-test for test work or business, integration, KPI, and probabilistic proof. Use best-practices when current external evidence can change a decision.
Then write the plan and chronicle.
In chat, cover result, checks, what is out of scope, approach, files, and risks. Offer the conversation-language equivalents of Approve / Edit / Cancel / Chat about, then stop. Only Approve after that presentation permits implementation; the original request does not.
After approval, implement, verify, explain concepts worth transferring, and review.
Create or update the repository plan and chronicle in completed tool calls before product or plugin edits. Never combine them in one patch. Record Current step: Implement, then complete Implement, Verify, Explain diff, and Review.
After Verify and before Review:
- a business, architectural, lifecycle, trade-off, or failure-mode concept exists → enter Explain diff;
- no concept is worth transferring → state that briefly and continue.
This gate does not affect Direct.
Translate older Claude Code tool names on Codex with codex-tools.md.
Source: hashgraph-online/awesome-codex-plugins → plugins/reidemeister94/development-skills/skills/using-development-skills/SKILL.md