Loading
Loading
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
written by Forgecat
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
ForgeCatnpx forgecat install @forgecat/anthropics_claude-plugins-official_feature-dev
| Field | Value |
|---|---|
| Author | Anthropic |
| Original repository | https://github.com/anthropics/claude-plugins-official/tree/main/plugins/feature-dev |
| Version | 0.0.0 |
| Original commit | cf62a6c |
| License | Apache-2.0 |
| Source platform | Claude Code plugin |
| Platform | Status |
|---|---|
| Claude Code | Tested |
| Cursor | Partial |
| Codex | Partial |
written by original source
A comprehensive, structured workflow for feature development with specialized agents for codebase exploration, architecture design, and quality review.
The Feature Development Plugin provides a systematic 7-phase approach to building new features. Instead of jumping straight into code, it guides you through understanding the codebase, asking clarifying questions, designing architecture, and ensuring quality—resulting in better-designed features that integrate seamlessly with your existing code.
Building features requires more than just writing code. You need to:
This plugin embeds these practices into a structured workflow that runs automatically when you use the /feature-dev command.
/feature-devLaunches a guided feature development workflow with 7 distinct phases.
Usage:
/feature-dev Add user authentication with OAuth
Or simply:
/feature-dev
The command will guide you through the entire process interactively.
Goal: Understand what needs to be built
What happens:
Example:
You: /feature-dev Add caching
Claude: Let me understand what you need...
- What should be cached? (API responses, computed values, etc.)
- What are your performance requirements?
- Do you have a preferred caching solution?
Goal: Understand relevant existing code and patterns
What happens:
code-explorer agents in parallelAgents launched:
Example output:
Found similar features:
- User authentication (src/auth/): Uses JWT tokens, middleware pattern
- Session management (src/session/): Redis-backed, 24hr expiry
- API security (src/api/middleware/): Rate limiting, CORS
Key files to understand:
- src/auth/AuthService.ts:45 - Core authentication logic
- src/middleware/authMiddleware.ts:12 - Request authentication
- src/config/security.ts:8 - Security configuration
Goal: Fill in gaps and resolve all ambiguities
What happens:
Example:
Before designing the architecture, I need to clarify:
1. OAuth provider: Which OAuth providers? (Google, GitHub, custom?)
2. User data: Store OAuth tokens or just user profile?
3. Existing auth: Replace current auth or add alongside?
4. Sessions: Integrate with existing session management?
5. Error handling: How to handle OAuth failures?
Critical: This phase ensures nothing is ambiguous before design begins.
Goal: Design multiple implementation approaches
What happens:
code-architect agents with different focuses:
Example output:
I've designed 3 approaches:
Approach 1: Minimal Changes
- Extend existing AuthService with OAuth methods
- Add new OAuth routes to existing auth router
- Minimal refactoring required
Pros: Fast, low risk
Cons: Couples OAuth to existing auth, harder to test
Approach 2: Clean Architecture
- New OAuthService with dedicated interface
- Separate OAuth router and middleware
- Refactor AuthService to use common interface
Pros: Clean separation, testable, maintainable
Cons: More files, more refactoring
Approach 3: Pragmatic Balance
- New OAuthProvider abstraction
- Integrate into existing AuthService
- Minimal refactoring, good boundaries
Pros: Balanced complexity and cleanliness
Cons: Some coupling remains
Recommendation: Approach 3 - gives you clean boundaries without
excessive refactoring, and fits your existing architecture well.
Which approach would you like to use?
Goal: Build the feature
What happens:
Notes:
Goal: Ensure code is simple, DRY, elegant, and functionally correct
What happens:
code-reviewer agents in parallel with different focuses:
Example output:
Code Review Results:
High Priority Issues:
1. Missing error handling in OAuth callback (src/auth/oauth.ts:67)
2. Memory leak: OAuth state not cleaned up (src/auth/oauth.ts:89)
Medium Priority:
1. Could simplify token refresh logic (src/auth/oauth.ts:120)
2. Consider extracting OAuth config validation
All tests pass. Code follows project conventions.
What would you like to do?
Goal: Document what was accomplished
What happens:
Example:
Feature Complete: OAuth Authentication
What was built:
- OAuth provider abstraction supporting Google and GitHub
- OAuth routes and middleware integrated with existing auth
- Token refresh and session integration
- Error handling for all OAuth flows
Key decisions:
- Used pragmatic approach with OAuthProvider abstraction
- Integrated with existing session management
- Added OAuth state to prevent CSRF
Files modified:
- src/auth/OAuthProvider.ts (new)
- src/auth/AuthService.ts
- src/routes/auth.ts
- src/middleware/authMiddleware.ts
Suggested next steps:
- Add tests for OAuth flows
- Add more OAuth providers (Microsoft, Apple)
- Update documentation
code-explorerPurpose: Deeply analyzes existing codebase features by tracing execution paths
Focus areas:
When triggered:
Output:
code-architectPurpose: Designs feature architectures and implementation blueprints
Focus areas:
When triggered:
Output:
code-reviewerPurpose: Reviews code for bugs, quality issues, and project conventions
Focus areas:
When triggered:
Output:
/feature-dev Add rate limiting to API endpoints
Let the workflow guide you through all 7 phases.
Explore a feature:
"Launch code-explorer to trace how authentication works"
Design architecture:
"Launch code-architect to design the caching layer"
Review code:
"Launch code-reviewer to check my recent changes"
Use for:
Don't use for:
Issue: Code exploration or architecture agents are slow
Solution:
Issue: Phase 3 asks too many questions
Solution:
Issue: Too many architecture options in Phase 4
Solution:
Sid Bidasaria (sbidasaria@anthropic.com)
1.0.0
None
forgecat
View CreatorNone