feature-builder

Name: feature-builder
Availability: InStock
Author: matthew-bram

Guide feature implementation through an 8-phase architecture-first workflow with documentation and quality gates.

Updated Dec 4, 2025

Search Tags:#workflow #architecture #documentation #feature development #quality gates #paired programming

Ready to run

npx skills add https://github.com/matthew-bram/enterprise-confluent-test-probe --skill feature-builder-matthew-bram

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-builder
Source: https://github.com/matthew-bram/enterprise-confluent-test-probe/tree/main/.claude/skills/feature-builder
Command: npx skills add https://github.com/matthew-bram/enterprise-confluent-test-probe --skill feature-builder-matthew-bram

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill prevents context loss and ensures architectural integrity by enforcing an 8-phase, documentation-first approach to feature development, promoting collaborative coding and quality gates.

Core Features & Use Cases

Structured Workflow: Guides features through 8 distinct phases, from architecture documentation to final validation.
Architecture-First: Mandates Phase 0 architecture documentation before any code is written, with strict approval gates.
Collaborative Development: Facilitates "two-in-the-box" paired programming, ensuring shared understanding and quality.
State Management: Tracks progress and decisions in working/{feature-name}-progress.md for session recovery.
Use Case: When starting a new feature, this skill ensures you document the architecture, get it approved, implement code, test thoroughly, and update documentation, guaranteeing a robust and well-understood deliverable.

Quick Start

Use the feature-builder skill to start developing a new feature, ensuring all architectural and documentation steps are followed.

Frequently Asked Questions about feature-builder

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

FAQPage Schema

How do I enforce architecture-first documentation before writing any code for a new feature?▼

Systematic feature development mandates Phase 0 architecture documentation before coding begins, requiring explicit user approval at strict quality gates to ensure architectural integrity and prevent context loss.

What is the best way to manage feature development state across multiple sessions?▼

Feature development state is managed across sessions by tracking progress and decisions in a dedicated markdown progress tracker, enabling seamless session recovery without losing architectural context or workflow status.

How does paired programming integrate into a structured feature development workflow?▼

Paired programming integrates into feature development through a collaborative 'two-in-the-box' approach, facilitating shared understanding and meeting quality gates via specialized agents for code review and documentation checks.

Can I use an 8-phase workflow for both feature implementation and final validation?▼

Yes, the 8-phase workflow guides feature implementation from initial architecture documentation through coding, thorough testing, and final validation, enforcing quality gates and documentation updates throughout the entire lifecycle.

When do I need explicit user approvals during structured feature development?▼

Explicit user approvals are required at critical junctures during feature development, specifically after Phase 0 architecture documentation and before proceeding through subsequent quality gates and validation phases.