بنقرة واحدة
plan
Create a new implementation plan in the repo's planning area.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create a new implementation plan in the repo's planning area.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review and update third-party dependencies. Use this when asked to upgrade packages, survey new minor or major releases for useful features, assess whether a repository can adopt them, or validate whether a release looks suspicious before bumping it.
Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots.
Run a security-focused code audit with a generic checklist first, then layer on repo-specific risks.
| name | plan |
| description | Create a new implementation plan in the repo's planning area. |
Create a new implementation plan in the repo's planning area.
$ARGUMENTS — A short slug for the plan, ideally kebab-case. If empty, derive a reasonable slug from the task.
Prefer this shared planning layout when the repo supports it:
.agents/ARCHITECTURE.md
.agents/GOALS.md
.agents/STATUS.md
.agents/plans/
If the repo uses a different planning area, adapt to it rather than creating duplicate systems.
Read planning context:
.agents/ARCHITECTURE.md if present.agents/GOALS.md if presentDetermine the plan location:
.agents/plans/Determine the next plan number:
ls .agents/plans/
Use the next sequential number when numbered plans are already in use. If the repo does not number plans, follow its established naming.
Research before writing:
Write the plan with this structure:
# Plan: [Feature Name]
Date: YYYY-MM-DD
## Goal
What are we building and why?
## Design Decisions
- **Decision**: Why this approach over alternatives.
## Scope
**In scope:**
- ...
**Out of scope:**
- ...
## Implementation
- `path/to/file` — what changes here
## Test Cases
What needs to be verified.
## Open Questions
Any unresolved decisions.
Plan well, do not over-specify:
Confirm before finalizing if the user is still shaping the task. If they asked you to just create the plan, go ahead and write it.