Enforce plan-driven coding governance for multi-part implementation workflows.
npx skills add https://github.com/hex0xdeadbeef/claude-kit --skill coder-rules
Please help me install this Agent Skill. Skill: coder-rules Source: https://github.com/hex0xdeadbeef/claude-kit/tree/main/.claude/skills/coder-rules Command: npx skills add https://github.com/hex0xdeadbeef/claude-kit --skill coder-rules
Coders often start implementations without a clear plan or evaluation criteria, which leads to scope creep and inconsistent handoffs. This skill provides a structured, plan-driven governance model that enforces a fixed sequence: load plan, evaluate feasibility, implement changes, verify, and deliver a handoff payload with documented resolutions and deviations.
Kick off a coder workflow with the plan, evaluating feasibility, implementing changes, verifying results, and preparing the handoff payload.
High-intent search queries and answers about installing and using this skill.
A plan-driven coding workflow prevents scope creep by enforcing a fixed sequence: load the plan, evaluate feasibility, implement changes, verify results, and deliver a structured handoff payload. This ensures strict adherence to defined rules and tracks deviations to preserve accountability.
The evaluate protocol decides whether to PROCEED, REVISE, or RETURN before implementation begins. This risk assessment step checks plan alignment and feasibility to ensure the coding task stays within scope before any changes are made.
A structured handoff payload for code reviewers includes documented resolutions and tracked deviations from the original plan. This structured handoff protocol preserves scope and accountability across multi-part coding iterations.
The critical rules for reliable implementation include plan-only execution, layer-dependency checks, domain cleanliness, no log+return patterns, and requiring tests to pass as gating conditions before proceeding with the workflow.
Yes, deviation tracking manages push-backs by documenting any departures from the original plan. This preserves scope and accountability by ensuring all deviations are recorded and reviewed during the handoff to code reviewers.
You should avoid plan-driven governance for simple, single-step coding modifications that do not require multi-part iterations, structured handoffs, or feasibility evaluations, as the overhead of deviation tracking and verification gating outweighs the benefits.
yu13130122297Identify uncertainties in research framing, datasets, metrics, and baselines.
wsmanVerify development story completion against acceptance criteria and governance artifacts.
AreteDriverImplements CI/CD pipelines using Batcomputer for automated code review and deployment gating.
mayurpiseExecute track plan tasks using a test-driven development workflow.
