skills.rest
ab300819
ab300819COMMUNITY
Explore all skills by this author →
GitHub

dev-flow

Implements tasks and fixes with contract-first TDD and gated evidence delivery.

Updated Jan 12, 2026
Search Tags:#tdd#code review#quality gates#task implementation#execution contract#batch development#red-green testing
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill dev-flow-ab300819
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-flow
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/dev-flow
Command: npx skills add https://github.com/ab300819/keel-workflow --skill dev-flow-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working outside a documentation-driven keel project, ad-hoc development often lacks acceptance criteria, test discipline, and review rigor. This Skill turns a plan document, task description, or issue text into a governed development run with explicit contracts, red-green testing, and evidence-based delivery. ## Core Features & Use Cases - Execution Contract Gate: Negotiates a YAML execution contract (scope, expected behavior, evidence plan, stop conditions) before any implementation begins. - Red-Green Enforcement: Requires failing tests before implementation, freezes tests during implementation, and declares degraded evidence when automated testing is infeasible instead of faking TDD. - Fresh-Context Verification: Dispatches a new-context sub-agent to independently verify diff-to-contract compliance, with out-of-contract findings deferred rather than silently fixed. - Batch Mode: Processes Markdown checklist plans item by item, each with fresh context, independent gates, atomic commits, and resumable progress. - Use Case: You receive a GitHub issue describing a bug in a project with no keel documentation. Provide the issue text, confirm the generated execution contract, and receive tested code plus a delivery report with evidence for each contracted behavior. ## Quick Start Ask the agent to implement the task described in your issue text or plan document using dev-flow, then confirm the proposed execution contract to begin development.

Frequently Asked Questions about dev-flow

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

FAQPage Schema
How do I run a development task without a full documentation workflow?▼

Provide a plan document path, task description, or issue text as input. The skill derives an execution contract with scope and expected behavior, asks for one confirmation, then implements with red-green testing and delivers an evidence-backed report.

What is the difference between dev-flow and dev-workflow?▼

Use dev-workflow when the project has keel documentation (docs/devdocs/) and tasks carry T-XX numbering with traceability. Use dev-flow for projects without keel docs, loose plans from tools like superpowers writing-plans, or plain issue-driven development.

Does dev-flow require automated tests to work?▼

No. When automated testing is infeasible (no test framework, pure config, exploratory tasks), the contract's evidence_plan must declare degraded evidence such as commands, screenshots, or manual verification along with the reason, rather than faking TDD.

Can dev-flow process a multi-item plan document in batch?▼

Yes. Each independently executable checklist item runs with fresh context and passes all three gates individually, then gets checked off and atomically committed. Re-reading the plan's checkbox state enables resumption without checkpoint files.

When should I use the --strict-tdd or --audit flags?▼

Use --strict-tdd for high-risk changes (auth, data-loss, schema, public-api) to enforce physically separated test and implementation agents. Use --audit to append a full adversarial review after the standard verification gate passes.

Related Skills

Explore More Software Engineering Skills→
jnMetaCodejnMetaCode
7.6k

writing-plans

Generate executable implementation roadmaps for multi-step software features.

Community
Advanced
hotriluanhotriluan

ck:code-review

Review code changes across PRs, commits, and codebase scans.

Community
Advanced
lee-tolee-to
56

aif-best-practices

Apply universal code-quality guidelines to software projects across languages and teams.

Community
Advanced
berkayturanciberkayturanci
4

keel-overnight

Process GitHub issues overnight using time-aware merge rules from .keel/project.yaml.

Community
Advanced