implement-plan

Translate feature specifications into deterministic test-first plans and deliverables inventories.

45|3|Updated Jul 10, 2023

Search Tags:#workflow #spec #plan #todo #software-engineering #deliverables #test-first

Ready to run

npx skills add https://github.com/incubateur-ademe/benefriches --skill implement-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/incubateur-ademe/benefriches/tree/main/.claude/skills/implement-plan
Command: npx skills add https://github.com/incubateur-ademe/benefriches --skill implement-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams convert a feature specification into a concrete, test-first plan, reducing ambiguity and accelerating delivery.

Core Features & Use Cases

Plan extraction: derive a complete set of deliverables and tests from the spec.
Test-first workflow: create a structured Todo inventory to drive development.
Validation-driven delivery: align production files with the plan and verification steps.

Quick Start

Start by providing a feature spec file to the skill. The skill will parse the spec, enumerate tests and production files, and guide you through implementing the feature with a test-first approach.

Frequently Asked Questions about implement-plan

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

FAQPage Schema

How do I convert a feature specification into a test-first development plan?▼

A test-first workflow derives structured Todo inventories directly from your feature specification. It enumerates required tests and production files, validating alignment to ensure deterministic, validation-driven delivery.

What is a deterministic deliverables inventory in software engineering?▼

A deterministic deliverables inventory is a structured set of extracted tasks and files derived from a spec. It tracks production changes and tests through a guided workflow to reduce ambiguity during feature delivery.

How do I extract deliverables and tests from a feature spec file?▼

You extract deliverables by parsing the feature spec through a structured workflow. This process enumerates the required test and production files, creating a tracked inventory for validation-driven development.

Does this test-first planning workflow require any external dependencies?▼

No external dependencies are required to run this test-first planning workflow. You simply provide a feature specification file, and the skill parses it internally to generate the deliverables and test todos.

When should I use a structured plan for feature delivery instead of ad-hoc coding?▼

You should use a structured plan when converting a feature specification into test-first deliverables to reduce ambiguity. It ensures validation-driven alignment between production files and the spec, which ad-hoc coding lacks.