plan

Files (1)

• SKILL.md

SKILL.md (first lines)

Analyze the current project and create a detailed implementation plan for: the task/scope the user described when invoking this skill (if none given, ask or infer from context)

Do the planning work yourself (read-only exploration — do not implement).

## Process
1. Explore the codebase structure; read key files related to the task.
2. Identify existing patterns, conventions, and dependencies — read code before planning, don't assume.
3. Break the feature into discrete, independently completable and testable tasks.
4. Order tasks by dependency (what must come first).
5. Identify risks and open questions; flag ambiguities rather than guessing.
6. Estimate relative complexity (S/M/L) per task.
7. Present the plan for approval before any implementation.

## Output Format
```
## Implementation Plan: [Feature Name]

### Overview
[1-2 sentence summary]

### Prerequisites
- [What must be in place first]

### Tasks
1. **[Task Name]** (Complexity: S/M/L)
   - Files: [files to create/modify]
   - Description: [what to do]
   - Tests: [what tests to write]

### Risks
- [Risk]: [Mitigation]

### Open Questions
- [Question needing user input]
```

From Hbin77/codex-kit, MIT.

More from Hbin77/codex-kit