feat-dev

Organize feature development into a seven-stage workflow with parallel agents.

12|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/FlameMida/spec-dev --skill feat-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feat-dev
Source: https://github.com/FlameMida/spec-dev/tree/main/skills/feat-dev
Command: npx skills add https://github.com/FlameMida/spec-dev --skill feat-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides an end-to-end, seven-stage workflow to systematically plan, implement, and review new features across cross-functional teams, reducing miscommunication and delivery risk.

Core Features & Use Cases

  • Orchestrates seven stages: requirement understanding, codebase exploration, clarification, architecture design, implementation, quality review, and summary.
  • Supports ultrathink/Sequential thinking for complex requirements.
  • Uses specialized agents: code-explorer, code-architect, code-reviewer to parallelize tasks.
  • Task List management, parallel execution, and MCP fallback (context7, exa).

Quick Start

Provide a concise feature brief to trigger the seven-stage workflow.

Frequently Asked Questions about feat-dev

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

FAQPage Schema
How do I manage end-to-end feature development across cross-functional teams?

End-to-end feature development can be managed through a seven-stage workflow that coordinates requirements, design, implementation, and review. This approach enforces stage order and user confirmations to reduce cross-team miscommunication and delivery risk.

How does parallel agent work function during codebase exploration and architecture design?

Parallel agent work functions by deploying specialized agents like code-explorer, code-architect, and code-reviewer to execute tasks simultaneously. This parallelism accelerates workflow stages while maintaining structured task list management.

Can I use MCP fallbacks to maintain progress during tooling disruptions?

Yes, you can use MCP fallbacks with context7 and exa to maintain progress during tooling disruptions. These fallbacks ensure the feature development workflow continues operating even when primary tooling encounters issues.

What is the best way to handle uncertain requirements and risk mitigation in feature delivery?

The best way to handle uncertain requirements and risk mitigation is using ultrathink and Sequential thinking within a phased delivery workflow. This enforces clarification stages and architecture decisions before implementation begins.

Do I need to provide a complete specification to trigger the feature development workflow?

No, you do not need a complete specification. Providing a concise feature brief is sufficient to trigger the seven-stage workflow, which then guides requirements understanding and clarification to resolve uncertainties.