implementation

Orchestrate ID-driven feature development with architecture decisions and TDD loop steps.

Updated Apr 17, 2026

Search Tags:#tdd #architecture #documentation #test-generation #stubs #id-driven

Ready to run

npx skills add https://github.com/nullhack/pytest-beehave --skill implementation-nullhack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/implementation
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill implementation-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates architecture decisions and the TDD loop in a focused, ID-driven workflow so teams can iterate on features with a single @id at a time.

Core Features & Use Cases

Prerequisites verification: reads docs, features, and package metadata to ensure discovery readiness.
Architecture-first workflow: defines domain boundaries, ADRs, and stub scaffolding before implementation.
TDD loop discipline: generates test stubs, updates signatures, and validates green tests one @id at a time.
Quality gates: enforces review, lint, and test-coverage milestones before handoff.
Use Case: a feature moves from discovery to green integration by coordinating docs, code stubs, ADRs, and tests.

Quick Start

Run the architecture + TDD workflow for a chosen feature to generate stubs, ADRs, and initial tests, then iterate until green.

Frequently Asked Questions about implementation

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

FAQPage Schema

How do I coordinate architecture decisions with TDD loops for feature development?▼

Coordinating architecture decisions with TDD loops requires an ID-driven workflow that defines domain boundaries, records ADRs, and generates test stubs before iterating on code until all tests pass.

What is an ID-driven workflow for test-driven development?▼

An ID-driven workflow for test-driven development processes one feature @id at a time, generating test stubs, updating signatures, and validating green tests to enforce strict TDD loop discipline.

How do I generate test stubs and ADRs from discovery documentation?▼

To generate test stubs and ADRs, first verify prerequisites by reading discovery docs and package metadata, then scaffold architecture-first domain stubs and record ADRs before writing tests.

Do I need discovery documentation before starting architecture-first TDD?▼

Yes, discovery documentation is required before starting architecture-first TDD; the workflow enforces reading discovery docs, features, and validating package structure to ensure project readiness.

What quality gates are enforced during TDD loop iteration?▼

Quality gates enforced during TDD loop iteration include mandatory review, lint, and test-coverage milestones that must pass before advancing the feature toward handoff and green integration.

When should I not use a single-feature ID-driven TDD workflow?▼

You should avoid a single-feature ID-driven TDD workflow when project prerequisites are missing, package structure is invalid, or discovery documentation is incomplete, as the workflow enforces readiness checks.