feature-implementation

Execute staged feature implementation with tests after each task.

Updated May 15, 2026
One-click install
npx skills add https://github.com/w020316/cautious-broccoli --skill feature-implementation-w020316
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implementation
Source: https://github.com/w020316/cautious-broccoli/tree/main/workflow/feature-implementation
Command: npx skills add https://github.com/w020316/cautious-broccoli --skill feature-implementation-w020316

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides developers to implement features in a strict stage-by-stage sequence, ensuring tests are written and executed after each task, with automatic progress reports once a stage completes.

Core Features & Use Cases

  • Stage-by-stage feature implementation following a predefined task plan.
  • Immediate test generation and test execution after every task completion.
  • Automatic phase completion reports and status updates to the task planning documentation.

Quick Start

Invoke the staged workflow by loading the feature plan, executing tasks in order, and generating a phase report after all tests pass.

Frequently Asked Questions about feature-implementation

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

FAQPage Schema
How do I implement features stage-by-stage with automatic test execution?

To implement features stage-by-stage with automatic test execution, you need a workflow that orchestrates tasks in sequence and generates immediate tests after each task completes. This approach enforces incremental validation and produces phase completion reports automatically.

What is test-driven feature implementation and how does it track progress?

Test-driven feature implementation is a development workflow that executes a predefined task plan in strict stages, running tests immediately after each task. It tracks progress by generating automatic status updates and phase completion reports directly in the planning documentation.

How do I generate phase completion reports during document-driven development?

You can generate phase completion reports during document-driven development by executing tasks in order and writing tests after every task. Once all tests pass for a stage, the workflow automatically updates the task planning documentation with status reports.

Does this stage-based workflow require any specific testing frameworks or dependencies?

This stage-based workflow operates without any specific external dependencies or testing frameworks. It orchestrates the document-driven execution and test automation logic directly, allowing you to apply it to projects requiring strict adherence to task plans.

What is the best way to ensure strict adherence to a task plan during development?

The best way to ensure strict adherence to a task plan is using a stage-driven coding workflow that validates each task with immediate tests before proceeding. This enforces incremental validation and generates phase reports to maintain document-driven execution.