build-feature

Build multi-layer product features with tests at each layer.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill build-feature-jnlanahan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-feature
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/4-Build-Feature
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill build-feature-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of building a feature in a way that matches your codebase’s real layering and conventions, without skipping required test coverage and end-to-end verification.

Core Features & Use Cases

  • Layered, TDD-style implementation: Plans and implements changes in coherent vertical slices (schema → storage → routes → hooks → components) with tests at each layer.
  • Adapts to actual project architecture: Detects your framework, DB/ORM, validation, and test stack, then mirrors the most representative existing feature patterns.
  • Plan-driven execution when available: Executes the existing .claude/plan.md if present; otherwise it interviews the user just enough to define the scope before coding.
  • Safety guardrails: Runs checks and tests after each layer, blocks progress on failures, and verifies end-to-end behavior including auth/ownership expectations.

Quick Start

Ask the AI to build a new feature by saying: "build-feature add a notes feature with schema, API, UI, and full tests following the repository’s existing patterns."

Frequently Asked Questions about build-feature

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

FAQPage Schema
How do I build a full-stack feature with tests at every layer?

To build a full-stack feature with tests at every layer, use a commit-per-layer TDD approach that implements schema, storage, API routes, client hooks, and UI components sequentially. It detects your existing conventions and runs tests after each vertical slice.

What is the best way to implement CRUD expansions with auth-protected workflows?

Implementing CRUD expansions with auth-protected workflows is best handled by building in coherent vertical slices with safety guardrails. This approach verifies end-to-end behavior including auth and ownership expectations while mirroring your existing codebase patterns.

How does pattern matching work when adding new features to an existing codebase?

Pattern matching for new features works by detecting your framework, DB/ORM, validation, and test stack, then mirroring the most representative existing feature patterns. This ensures new code adapts to your actual project architecture rather than imposing external conventions.

Can I execute a predefined plan for feature implementation?

Yes, you can execute a predefined plan for feature implementation if a .claude/plan.md file is present in your project. If the plan file is missing, it will interview you to define the required scope before coding begins.

Does TDD-style feature implementation block progress when tests fail?

TDD-style feature implementation does block progress when tests fail. It runs checks and tests after completing each layer and halts development on failures to ensure end-to-end verification and production readiness before moving forward.