comprehensive-feature-builder

Coordinate five-phase feature development with checkpoints and Playwright MCP validation.

3|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/nano-step/skill-manager --skill comprehensive-feature-builder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comprehensive-feature-builder
Source: https://github.com/nano-step/skill-manager/tree/main/skills/comprehensive-feature-builder
Command: npx skills add https://github.com/nano-step/skill-manager --skill comprehensive-feature-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic, checkpoint-based workflow that guides teams from idea to validated feature, reducing token bloat and fragmentation by saving progress at each phase.

Core Features & Use Cases

  • Structured 5-phase process: Discovery, Analysis, Design, Implementation, and Testing with built-in checklists and reports.
  • Traceability and checkpoints: Saves reports and progress to files to enable re-entry and auditing.
  • OpenSpec integration & E2E validation: Creates OpenSpec proposals and generates Playwright MCP-based tests to verify features.
  • Use Case: Team wants to research, design, implement, and verify a major feature with auditable artifacts and reproducible tests.

Quick Start

Begin Phase 1: Discovery and follow the five-phase workflow to research, design, implement, and validate the feature.

Frequently Asked Questions about comprehensive-feature-builder

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

FAQPage Schema
How do I manage feature development workflow from discovery to e2e testing without token bloat?▼

A structured feature workflow prevents token bloat by using a five-phase process with checkpoints. This approach saves progress and reports to files at each phase, enabling re-entry and auditing while reducing context fragmentation.

What is the best way to structure feature implementation and ensure traceability across phases?▼

The best way to structure feature implementation is through a five-phase workflow: Discovery, Analysis, Design, Implementation, and Testing. It enforces structured phase artifacts and OpenSpec proposals to maintain full traceability across the codebase.

How do I generate Playwright e2e tests for a new feature automatically?▼

Playwright e2e tests are generated during the testing phase of the workflow. The process uses Playwright MCP to create automated end-to-end validation tests, ensuring the implemented feature works as designed.

Does this feature workflow support OpenSpec proposals for product initiatives?▼

Yes, the feature workflow supports OpenSpec proposals. It creates OpenSpec proposals when needed during the design phase to coordinate product initiatives and maintain structured documentation across the feature lifecycle.

Can I use this checkpoint-based workflow for both codebase features and broader product initiatives?▼

Yes, the checkpoint-based workflow applies to both codebase features and product initiatives. It coordinates end-to-end feature development tasks across discovery, design, implementation, and testing with built-in checklists.