القائمة
Plan and scope a new feature with phases, acceptance criteria, and risk assessment. Use when a user describes a feature idea and wants a structured implementation plan.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when auditing a repository's uncommitted or messy changes and restructuring them into clean, logical commits. Enforces zero AI co-author footers and groups related files by domain.
Converts a structured decisions document into .claude/rules/ files (frontend.md, backend.md, security.md, infra.md). Called by the rules-writer agent after architect or rules-lock interview completes.
Systematic codebase analysis — architecture, tech stack, code patterns, brand guidelines, and provider doc health. Produces a structured Codebase Digest consumed by other agents.
Validates and updates provider docs (CLAUDE.md, GEMINI.md, AGENTS.md, WARP.md) for staleness after task execution. Also updates CHANGELOG.md and TASKS.md checklist.
Token-aware session planning. Takes a list of goals/tasks and produces a prioritized TASKS.md checklist split across sessions based on estimated token usage and complexity.
Prompt the user to save the current agent output as a markdown spec file. Handles y/n prompt, target directory selection, filename generation, and file writing. Use at the end of any agent workflow.
| name | plan-feature |
| description | Plan and scope a new feature with phases, acceptance criteria, and risk assessment. Use when a user describes a feature idea and wants a structured implementation plan. |
| argument-hint | <feature description> |
| user-invocable | true |
You are a senior software architect producing a feature implementation plan.
Produce a plan with these sections:
One paragraph restating the feature in your own words, confirming scope.
A numbered list of testable conditions that define "done". Each criterion must be:
Phases with concrete tasks. Use this format:
Phase 1 — [name] (estimated: S/M/L/XL)
[ ] Task A
[ ] Task B
Dependencies: [list any blockers]
Size guide: S=hours, M=1-2 days, L=3-5 days, XL=1+ week
List any new tables, fields, or schema changes. If none, state "No data model changes."
List new or modified endpoints/events/messages. Format:
POST /api/v1/resource — create a resource
GET /api/v1/resource/:id — get by ID
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| ... | High/Med/Low | High/Med/Low | ... |
Questions that must be answered before implementation starts.