rune-cook

Orchestrates feature implementation through a phased TDD workflow with quality gates.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-cook-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-cook
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-cook
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-cook-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code changes made without structure lead to skipped tests, unreviewed plans, and untracked decisions. This Skill routes every code modification through a disciplined pipeline — understand, plan, test, implement, quality check, verify, commit — so nothing ships without evidence. ## Core Features & Use Cases - Phased TDD Pipeline: Runs an 8-phase workflow (understand → plan → test → implement → quality → verify → commit → bridge) with hard gates between phases and mandatory user plan approval. - Adaptive Rigor Scaling: Auto-detects task complexity via a risk-scored rigor assessment, selecting nano, fast, bugfix, refactor, feature, security, or hotfix workflow chains. - Quality Gates & Recovery: Coordinates staged preflight, security, review, and completion-gate checks with remediation cycle caps, loop detection, and an approach-pivot escalation chain. - Use Case: Ask the agent to add a payment retry feature; it scouts the codebase, drafts an approved plan, writes a failing test, implements the minimal fix, runs security and review gates, then commits with a semantic message. ## Quick Start Ask the agent to implement a new feature or fix a bug, and it will route the request through the full cook pipeline starting with codebase understanding and an approval-gated plan.

Frequently Asked Questions about rune-cook

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

FAQPage Schema
How do I implement a new feature with test-driven development?

Invoke the cook workflow with a feature request; it scouts the codebase, produces an approved plan, writes one failing test, implements the minimal code to pass it, then runs quality gates before committing. Each phase has a hard gate so no step is skipped.

What workflow should I use for a production hotfix?

Use the hotfix chain, which runs contain, branch, fix, verify, security check, deploy, watchdog, and postmortem steps. For non-incident dev-time fixes it shortens to fix, verify, and commit.

Can small changes skip the full TDD pipeline?

Yes. Fast mode activates for changes under 30 lines in a single non-security file, skipping plan and test phases while keeping preflight and verification. Nano mode handles trivial tasks like config edits with direct execution and verification.

Does the workflow handle breaking API changes?

Yes. Phase 2.5 enforces an RFC gate: any breaking change to public APIs, database schemas, or auth flows requires a written RFC artifact with migration path and explicit user approval before implementation begins.

What happens when the implementation gets stuck in a debug loop?

After three debug-fix loops the workflow triggers a re-plan, then an approach pivot via rescue-mode brainstorming before escalating to the user. Hard caps on fixes and quality loops prevent runaway iterations.