build-unplanned-feature

Orchestrate end-to-end feature development from a description using TDD and a worktree workflow.

41|4|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/etr/groundwork --skill build-unplanned-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-unplanned-feature
Source: https://github.com/etr/groundwork/tree/main/skills/build-unplanned-feature
Command: npx skills add https://github.com/etr/groundwork --skill build-unplanned-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically orchestrate end-to-end feature development from a description when no predefined tasks exist, guiding you from concept to shippable feature.

Core Features & Use Cases

  • Requirement gathering, architecture alignment, and task scoping.
  • TDD-driven implementation with a dedicated worktree workflow.
  • Multi-agent validation and structured handoffs to the base branch.

Quick Start

Provide a feature description or specify one, and the system will orchestrate requirement gathering, implementation, validation, and ready-to-merge handoffs.

Frequently Asked Questions about build-unplanned-feature

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

FAQPage Schema
How do I start feature development when I only have a vague idea and no task definitions?

Feature development from a vague idea requires automated requirement gathering and task scoping. This skill orchestrates end-to-end implementation, aligning architecture and enforcing project context to transform descriptions into shippable features.

How does TDD-based implementation work within a git worktree workflow?

TDD-based implementation within a git worktree workflow isolates feature changes in a dedicated branch. The system coordinates test-driven coding and multi-agent validation, ensuring structured handoffs before merging back to the base branch.

What is the best way to automate architectural alignment and requirement gathering for a new feature?

Automating architectural alignment and requirement gathering involves coordinating task scoping with project context and naming conventions. This skill enforces these constraints automatically, guiding development from concept to a ready-to-merge state.

Can I use multi-agent validation to verify feature implementation before merging to the base branch?

Multi-agent validation verifies feature implementation before merging to the base branch. It operates within a controlled worktree workflow, running TDD-based checks and enforcing structured handoffs to ensure the feature meets project standards.

Does this feature development workflow require predefined tasks or existing task definitions?

This feature development workflow does not require predefined tasks or existing task definitions. It automates end-to-end orchestration directly from a feature description, handling requirement gathering and task scoping automatically.

When should I avoid using an automated end-to-end feature development orchestration system?

Avoid automated end-to-end feature development orchestration if your project lacks clear architectural conventions or if the feature description is too ambiguous for automated requirement gathering and multi-agent validation to enforce context accurately.