feature-dev

Coordinate end-to-end feature development with documentation-first, test-driven workflows.

1|Updated Nov 25, 2021
One-click install
npx skills add https://github.com/budmonde/dotfiles --skill feature-dev-budmonde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-dev
Source: https://github.com/budmonde/dotfiles/tree/main/opencode/skills/feature-dev
Command: npx skills add https://github.com/budmonde/dotfiles --skill feature-dev-budmonde

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end feature development by enforcing a documentation-first approach and a test-driven workflow, reducing ambiguity and rework across multiple files and teams.

Core Features & Use Cases

  • Documentation-first planning to align stakeholders before coding.
  • Test-driven development to define expected behavior and drive implementation.
  • Atomic commits and explicit state visibility via STATE.md and AGENTS/STATE.md, enabling faster reviews.
  • Structured project documentation scaffolding (AGENTS.md, AGENTS/STATE.md, AGENTS/TODO.md) to keep work organized and traceable.

Quick Start

Create the AGENTS.md scaffold and initial AGENTS/STATE.md, then draft an initial AGENTS/TODO.md item to begin the workflow.

Frequently Asked Questions about feature-dev

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

FAQPage Schema
How do I coordinate end-to-end feature development across multiple files and teams?

Coordinate end-to-end feature development by enforcing a documentation-first approach and test-driven workflow, reducing ambiguity and rework across multiple files and teams. It scaffolds structured project documentation to keep work organized and traceable.

What is documentation-first planning for agile feature development?

Documentation-first planning for agile feature development aligns stakeholders before coding begins. It enforces YAML frontmatter in SKILL.md and scaffolds structured project documentation like AGENTS.md and STATE.md to keep work organized and traceable.

How do I start a test-driven feature development workflow?

To start a test-driven feature development workflow, create the AGENTS.md scaffold and initial AGENTS/STATE.md, then draft an initial AGENTS/TODO.md item. This begins the structured workflow that defines expected behavior to drive implementation.

Can I use this test-driven workflow for medium-to-large features?

Yes, this test-driven workflow is explicitly applied to medium-to-large features that span multiple files and teams. It handles planning, implementation, testing, and documentation updates for complex feature development.

Why does test-driven development reduce rework in feature development?

Test-driven development reduces rework by defining expected behavior upfront to drive implementation. Combined with documentation-first planning, it reduces ambiguity across teams and enables faster reviews through atomic commits and explicit state visibility.

What's the best way to maintain state visibility during multi-team feature development?

Maintain state visibility during multi-team feature development by tracking progress through STATE.md and AGENTS/STATE.md files. This structured documentation approach enables explicit state tracking and faster reviews across distributed teams.