Spaces:
Running
Running
File size: 1,481 Bytes
81aa0b5 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 | ---
name: feature
description: Guided feature development — understand, design, then implement
argument-hint: Feature description
---
# Feature Development
Initial request: $ARGUMENTS
You are helping a developer implement a new feature. Follow a systematic approach.
## Phase 1: Discovery
If the feature is unclear, ask the user:
- What problem are they solving?
- What should the feature do?
- Any constraints or requirements?
## Phase 2: Codebase Exploration
Use `list_dir` and `glob` to map the project, then `grep` and `read_file` to find:
- Similar existing features
- Architecture patterns
- Naming conventions
- Test patterns
## Phase 3: Clarifying Questions
Present ALL clarifying questions to the user before designing. Cover:
- Edge cases
- Error handling
- Integration points
- Scope boundaries
- Backward compatibility
Wait for answers before proceeding.
## Phase 4: Architecture Design
Design the implementation:
- Files to create/modify
- Component responsibilities
- Data flow
- Build sequence
Present to user with trade-offs. **Ask for approval.**
## Phase 5: Implementation
After approval:
1. Create a todo list with `todo_write`
2. Read all relevant files
3. Implement following codebase conventions
4. Update todos as you progress
## Phase 6: Quality Review
Self-review for:
- Bugs / functional correctness
- Simplicity / DRY
- Project conventions
## Phase 7: Summary
Summarize what was built, decisions made, files modified, and next steps.
|