OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add secondsky/claude-skills --skill feature-dev
Automate 7-phase feature development with specialized agents (code-explorer, code-architect, code-reviewer). Use for multi-file features, architectural decisions, or encountering ambiguous requirements, integration patterns, design approach errors.
npx skills add secondsky/claude-skills --skill feature-dev
A comprehensive, structured workflow for feature development with specialized agents for codebase exploration, architecture design, and quality review.
Launch the guided feature development workflow:
Or interactively:
The workflow will guide you through 7 distinct phases automatically.
Building features requires more than just writing code. This skill provides a systematic approach that:
Goal: Understand what needs to be built
Example:
Goal: Understand relevant existing code and patterns
code-explorer agents in parallelAgents launched:
Example output:
Goal: Fill in gaps and resolve all ambiguities
Example:
Critical: Ensures nothing is ambiguous before design begins.
Goal: Design multiple implementation approaches
code-architect agents with different focuses:
Example output:
Goal: Build the feature
Goal: Ensure code is simple, DRY, elegant, and functionally correct
code-reviewer agents in parallel:
Example output:
Goal: Document what was accomplished
Purpose: Deeply analyzes existing codebase features by tracing execution paths
Focus:
Output:
Triggered: Automatically in Phase 2, or manually
Purpose: Designs feature architectures and implementation blueprints
Focus:
Output:
Triggered: Automatically in Phase 4, or manually
Purpose: Reviews code for bugs, quality issues, and project conventions
Focus:
Output:
Triggered: Automatically in Phase 6, or manually
Explore a feature:
Design architecture:
Review code:
Use for:
Don't use for:
Cause: Normal for large codebases Solution: Agents run in parallel when possible. Thoroughness pays off in better understanding.
Cause: Feature request too vague Solution: Be more specific in initial request. Provide context about constraints upfront.
Cause: Multiple valid approaches presented Solution: Trust the recommendation (based on codebase analysis). Pick pragmatic option when in doubt.
After using the workflow:
For detailed workflow documentation, see README.md
For agent specifications, see:
agents/code-explorer.mdagents/code-architect.mdagents/code-reviewer.mdFor slash command implementation, see commands/feature-dev.md
Found similar features:
- User authentication (src/auth/): Uses JWT tokens, middleware pattern
- Session management (src/session/): Redis-backed, 24hr expiry
Key files:
- src/auth/AuthService.ts:45 - Core authentication logic
- src/middleware/authMiddleware.ts:12 - Request authenticationBefore designing, I need to clarify:
1. OAuth provider: Which providers? (Google, GitHub, custom?)
2. User data: Store OAuth tokens or just profile?
3. Existing auth: Replace or add alongside current auth?
4. Sessions: Integrate with existing session management?
5. Error handling: How to handle OAuth failures?Approach 1: Minimal Changes
- Extend existing AuthService with OAuth methods
Pros: Fast, low risk
Cons: Couples OAuth to existing auth
Approach 2: Clean Architecture
- New OAuthService with dedicated interface
Pros: Clean separation, testable
Cons: More files, more refactoring
Approach 3: Pragmatic Balance
- New OAuthProvider abstraction
Pros: Balanced complexity and cleanliness
Cons: Some coupling remains
Recommendation: Approach 3 - clean boundaries without excessive refactoringHigh 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)
What would you like to do?/feature-dev Add rate limiting to API endpoints"Launch code-explorer to trace how authentication works""Launch code-architect to design the caching layer""Launch code-reviewer to check my recent changes"