
feature-implementation
by chernobelenkiy
SKILL.md
name: feature-implementation description: Orchestrates full feature implementation using Standard, TDD, or BDD workflows with automated quality gates.
Feature Implementation Skill
When to Use This Skill
- User wants to implement a new feature from scratch.
- User wants to use a specific methodology like TDD (Tests-First) or BDD (Behavior-Driven).
- User wants a structured, production-ready implementation with full verification.
- User wants to ensure that all requirements and expert recommendations are tracked and verified.
How It Works
This skill selects and orchestrates one of three specialized pipelines based on the task complexity and user preference. Each pipeline is defined in the workflows/ directory:
- Standard Workflow: Rapid implementation with tests following the code. (See
workflows/standard.md) - TDD Workflow: Rigorous unit-testing from the start (Red-Green-Refactor). (See
workflows/tdd.md) - BDD Workflow: High-level business scenarios (Gherkin) driving the implementation. (See
workflows/bdd.md)
All workflows follow a mandatory Build Verification phase using the build-verificator agent to ensure 100% completeness.
Procedure
Phase 1: Planning (Shared)
Follow the planning principles defined in each workflow:
- Audit codebase for reusable patterns.
- Identify integration surfaces.
- Gather recommendations from other agents in the history.
- Get explicit approval on the roadmap.
Phase 2: Execution
Option A: Standard Workflow
Follow the stages in workflows/standard.md:
- Implement: Write production-ready code.
- Test: Write and run unit tests to confirm implementation.
- Refactor: Clean up and simplify while keeping tests green.
Option B: TDD Workflow (Red-Green-Refactor)
Follow the stages in workflows/tdd.md:
- Red: Write failing unit tests first. Run them to confirm failure.
- Green: Write minimum code to make tests pass.
- Refactor: Improve quality while keeping tests green.
Option C: BDD Workflow
Follow the stages in workflows/bdd.md:
- Spec: Write Gherkin scenarios (
.feature) and failing technical tests. - Implement: Write code to satisfy both business and technical specs.
- Refactor: Simplify and optimize.
Phase 3: Quality Gates (Build Verification)
The build-verificator agent performs the final audit as described in each workflow:
- Build Check: Ensures the project compiles.
- Test Check: Ensures 100% test pass rate.
- Requirement Audit: Maps implementation back to the original plan.
- Recommendation Audit: Verifies that all expert feedback from the conversation was either implemented, communicated, or roadmaped.
Important Rules
| Rule | Description |
|---|---|
| No Placeholders | Never leave TODO or FIXME. Implementation must be complete. |
| Verification Gate | Never mark a task as "Done" without a successful Build Verification Report. |
| Sequential Phases | Complete each phase fully before moving to the next. |
| Audit First | Always check for existing code to reuse before writing new logic. |
| POC First | If hypothesis is dubious or confidence is low, prioritize creating a POC first. |
Examples
- User: "Add a login form with validation." -> Use Standard or TDD.
- User: "Implement the checkout flow described in this Gherkin file." -> Use BDD.
- User: "I need a super robust calculation engine for the bank." -> Use TDD.
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon