Help us improve
Share bugs, ideas, or general feedback.
From fullstack-dev
Guided feature development with codebase understanding and architecture focus
npx claudepluginhub Byunk/claude-code-toolkit --plugin fullstack-devHow this command is triggered — by the user, by Claude, or both
Slash command
/fullstack-dev:feature-dev Describe the feature in detailThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Feature Development You are orchestrating feature development using an architecture-first approach. Focus on high-level coordination and let specialized agents handle implementation details. ## Initial Request $ARGUMENTS ## Workflow Use TodoWrite to track progress through these phases: ### 1. Context Gathering Analyze the codebase to understand current architecture and patterns: - Identify framework, tech stack, and project structure - Map existing components, APIs, and database patterns - Review code conventions and architectural decisions - Document findings with file:line refere...
/feature-devGuides feature implementation: explores codebase with agents, asks clarifying questions on ambiguities, designs architecture, and applies code changes.
/sc-workflowGuides feature development via phases: codebase exploration with agents, clarifying questions, architecture design, and step-by-step implementation.
/feature-devGuides feature development through structured phases: discovery, codebase exploration, architecture design, implementation with TDD, quality review, and summary.
/feature-devGuides feature implementation: explores codebase with agents, asks clarifying questions on ambiguities, designs architecture, and applies code changes.
/feature-devGuides feature development systematically: clarifies requirements, explores codebase with agents, resolves ambiguities, designs architecture, implements code for Python/Flask/Firebase projects.
Share bugs, ideas, or general feedback.
You are orchestrating feature development using an architecture-first approach. Focus on high-level coordination and let specialized agents handle implementation details.
$ARGUMENTS
Use TodoWrite to track progress through these phases:
Analyze the codebase to understand current architecture and patterns:
This helps you ask informed clarifying questions in the next phase.
Based on gathered context, use AskUserQuestion to clarify ALL requirements before proceeding:
Get complete, unambiguous requirements before moving to architecture design.
Launch the system-architect agent with complete requirements:
The architecture blueprint will include API contracts, frontend structure, data models, and system boundaries.
Present the architecture blueprint to the user:
If changes are needed, refine the architecture and get approval again.
Based on the approved architecture, determine affected domains and create implementation tasks.
Task Planning:
Sequential Execution: For each task, launch the appropriate agent with:
Domain Agents:
For complex domains (e.g., multi-page frontend with many components):
Agent Autonomy:
Once all implementation tasks complete, provide final summary:
CRITICAL: You handle ALL user interaction. Agents receive complete requirements and execute autonomously. Never delegate user questions to agents.