بنقرة واحدة
plan
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Comprehensive onboarding for new or returning contributors. Scans repository artifacts (git history, CLAUDE.md / AGENTS.md, project rules, skill catalog, DESIGN.md, research & library notes, checkpoints, agent-team logs) and synthesizes a GUIDE.md at the repository root summarizing what has been worked on, why, and how to resume work.
Save full session context: git history, CLI consultations, Agent Teams activity, and discover reusable skill patterns — all in one run. No flags needed. Maintains a rolling PROGRESS.md (latest 5 checkpoint summaries) and ends with a compact phase that prunes stale CLAUDE.md Zone C work blocks and compacts the conversation (also available standalone via --compact-only, replacing the old /context-refresh skill). Run at session end, after major milestones, or when you want to capture learnings.
Codex CLI handles planning, design, and complex code implementation. Use for: architecture design, implementation planning, complex algorithms, debugging (root cause analysis), trade-off evaluation, code review. External research is NOT Codex's job — use general-purpose-opus instead. Explicit triggers: "plan", "design", "architecture", "think deeper", "analyze", "debug", "complex", "optimize".
Unified feature planning & implementation skill — replaces the old /add-feature and /start-feature skills (both trigger phrases still apply here). MODE=existing (formerly /add-feature): add a feature to an established codebase with Codex-first collaboration — Codex is consulted in every phase for scope analysis, architecture design, implementation planning, and validation. MODE=greenfield (formerly /start-feature): start a large or new feature that requires external research — Agent Teams (Researcher + Architect) do parallel research & design. Both modes share Phase 3 complexity routing (SIMPLE: Codex direct, MODERATE: Codex + /team-execute --review-only, COMPLEX: /team-execute).
Analyze project structure, write the thick requirements doc (.claude/docs/DESIGN.md), and populate the thin "Repository Identity" pointer in CLAUDE.md (Zone B).
Research a library and create comprehensive documentation in .claude/docs/libraries/.
| name | plan |
| description | Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding. |
| disable-model-invocation | true |
Create an implementation plan for $ARGUMENTS.
First clarify:
Investigate the codebase:
- Related existing code
- Files affected
- Libraries/patterns to use
- Existing tests
Break into small steps:
## Implementation Plan: {Title}
### Purpose
{1-2 sentences}
### Scope
- New files: {list}
- Modified files: {list}
- Dependencies: {list}
### Implementation Steps
#### Step 1: {Title}
- [ ] {Specific task}
- [ ] {Specific task}
**Verification**: {Completion criteria for this step}
#### Step 2: {Title}
...
### Risks & Considerations
- {Potential issues and mitigations}
### Open Questions
- {Items to clarify before implementation}