mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-03 15:43:31 +08:00
4813ed753f
Ports functionality from 10+ separate plugins into ECC so users only need one plugin installed. Consolidates: pr-review-toolkit, feature-dev, commit-commands, hookify, code-simplifier, security-guidance, frontend-design, explanatory-output-style, and personal skills. New agents (8): code-architect, code-explorer, code-simplifier, comment-analyzer, conversation-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer New commands (9): commit, commit-push-pr, clean-gone, review-pr, feature-dev, hookify, hookify-list, hookify-configure, hookify-help New skills (8): frontend-design, hookify-rules, github-ops, knowledge-ops, lead-intelligence, oura-health, pmx-guidelines, remotion Enhanced skills (8): article-writing, content-engine, market-research, investor-materials, investor-outreach, x-api, security-scan, autonomous-loops — merged with personal skill content New hook: security-reminder.py (pattern-based OWASP vulnerability warnings on file edits) Totals: 36 agents, 69 commands, 128 skills, 29 hook scripts
46 lines
1.7 KiB
Markdown
46 lines
1.7 KiB
Markdown
---
|
|
description: Guided feature development with codebase understanding and architecture focus
|
|
---
|
|
|
|
A structured 7-phase feature development workflow that emphasizes understanding existing code before writing new code.
|
|
|
|
## Phases
|
|
|
|
### Phase 1: Discovery
|
|
- Read the user's feature request carefully
|
|
- Identify key requirements, constraints, and acceptance criteria
|
|
- Ask clarifying questions if the request is ambiguous
|
|
|
|
### Phase 2: Codebase Exploration
|
|
- Use the **code-explorer** agent to deeply analyze relevant existing code
|
|
- Trace execution paths and map architecture layers
|
|
- Understand existing patterns, abstractions, and conventions
|
|
- Document dependencies and integration points
|
|
|
|
### Phase 3: Clarifying Questions
|
|
- Present findings from exploration to the user
|
|
- Ask targeted questions about design decisions, edge cases, and preferences
|
|
- **Wait for user response before proceeding**
|
|
|
|
### Phase 4: Architecture Design
|
|
- Use the **code-architect** agent to design the feature architecture
|
|
- Provide implementation blueprint: files to create/modify, component designs, data flows
|
|
- Present the plan to the user for approval
|
|
- **Wait for user approval before implementing**
|
|
|
|
### Phase 5: Implementation
|
|
- Implement the feature following the approved architecture
|
|
- Use TDD approach: write tests first, then implementation
|
|
- Follow existing codebase patterns and conventions
|
|
- Make small, focused commits
|
|
|
|
### Phase 6: Quality Review
|
|
- Use the **code-reviewer** agent to review the implementation
|
|
- Address Critical and Important issues
|
|
- Verify test coverage meets requirements
|
|
|
|
### Phase 7: Summary
|
|
- Summarize what was built and how it integrates
|
|
- List any follow-up items or known limitations
|
|
- Provide testing instructions
|