devbooks-coder

Automate coder implementation workflows with tasks.md adherence and gate-based verification.

84|6|Updated Jan 12, 2026

Search Tags:#workflow #development #evidence #gates #tests #tasks.md #coder

Ready to run

npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-coder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devbooks-coder
Source: https://github.com/Darkbluelr/dev-playbooks-cn/tree/main/skills/devbooks-coder
Command: npx skills add https://github.com/Darkbluelr/dev-playbooks-cn --skill devbooks-coder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the coder's end-to-end implementation workflow to strictly follow tasks.md, run gate checks, and ensure no modifications to tests, providing auditable traceability and evidence-driven delivery.

Core Features & Use Cases

Strict coder role execution: implements tasks.md items exactly and validates against tests and static checks.
Evidence-driven delivery: saves green evidence to the change package and uses gate-based validation for progress.
Gate-based workflow: enforces Knife-style slicing and gates to block progression on failures and ensure auditable outcomes.
Real-time progress tracking: maintains per-task status and prevents silent approvals.
Use cases: when organizations require auditable, test-driven delivery and strict separation of duties between roles.

Quick Start

Follow the tasks.md plan, implement all tasks, and verify gates by running the tests to produce green evidence.

Frequently Asked Questions about devbooks-coder

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

FAQPage Schema

How do I automate test-driven delivery to ensure strict adherence to tasks.md?▼

Automate test-driven delivery by enforcing tasks.md adherence and gate-based verification to validate implementations. This workflow forbids test modifications and requires verifiable evidence through tests, static checks, and builds to ensure auditable traceability.

What is gate-based verification for software engineering workflows?▼

Gate-based verification is a mechanism that enforces Knife-style slicing to block progression on failures. It validates progress through tests, static checks, and builds, ensuring auditable outcomes and preventing silent approvals during the implementation workflow.

How do I generate auditable evidence for code implementation tasks?▼

Generate auditable evidence by running tests and static checks to produce green evidence after implementing tasks.md items. The workflow saves this evidence to the change package and uses gate-based validation for structured progress tracking.

Can I modify tests to force a green build during the implementation workflow?▼

No, you cannot modify tests to force a green build during the implementation workflow. The protocol explicitly forbids test modifications, requiring verifiable evidence through original tests, static checks, and builds to ensure strict separation of duties.

How do I track real-time progress for per-task implementation status?▼

Track real-time progress by maintaining per-task status within the workflow, which prevents silent approvals. The system provides structured outputs for progress and evidence, routing failures to CI gates to block further progression until resolved.