build-feature

Automates full-stack feature implementation from an approved plan across database, API, frontend, and tests.

12|4|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/andrewvaughan/agent-council --skill build-feature-andrewvaughan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-feature
Source: https://github.com/andrewvaughan/agent-council/tree/main/canonical/skills/build-feature
Command: npx skills add https://github.com/andrewvaughan/agent-council --skill build-feature-andrewvaughan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end delivery of new features by translating an approved plan into multi-layer code across database, API, frontend, and tests, reducing manual integration effort and errors.

Core Features & Use Cases

  • Executes full-stack feature implementation aligned with an approved plan.
  • Coordinates changes across database schemas, backend services, frontend components, and test suites.
  • Use Case: When a plan-feature decision is ready, run the workflow to implement the feature and surface decisions for review.

Quick Start

Load the approved plan from /plan-feature and run the full-stack build across the database, API, frontend, and tests.

Frequently Asked Questions about build-feature

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

FAQPage Schema
How do I automate end-to-end feature implementation across database, backend, and frontend layers?

Automating end-to-end feature implementation requires translating an approved plan into a multi-layer codebase. This workflow coordinates database, backend, frontend, and testing changes to reduce manual integration effort and errors.

What is the best way to coordinate full-stack code commits from a single approved plan?

Coordinating full-stack code commits from an approved plan involves scoping tasks, managing branches, and tracking in-progress changes across database, API, and frontend layers before preparing for code review.

Do I need an approved plan before running a full-stack feature build?

Yes, you need an approved plan before running a full-stack feature build. The workflow loads an approved plan from plan-feature and translates it into multi-layer codebase changes across database, API, frontend, and tests.

Can I use council-guided product development for database migration planning and frontend testing?

Council-guided product development supports database migration planning and frontend testing by coordinating multi-layer codebase changes. It aligns database schemas, backend services, frontend components, and test suites with the approved plan.

How does in-progress tracking work for multi-layer codebase feature builds?

In-progress tracking for multi-layer codebase feature builds monitors task scoping, branch management, and commits across database, API, and frontend layers, surfacing decisions for review before final code submission.

When should I avoid automating end-to-end feature builds?

You should avoid automating end-to-end feature builds when a plan is not ready or when features require custom integration outside standard database, backend, frontend, and testing workflows that council input cannot scope.