القائمة
Sequence work before execution. Use for planning requests like "break this down", "roadmap", "approach", "milestones", "how should we proceed", migration planning, rollout planning, and scoped next steps.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review any artifact and output results in a Retrospective board format — what is well, what is bad, what should be improved, what to change. Use when the user says "review", "critique", "evaluate", "what's wrong with", "compare", or passes a skill, rule, doc, spec, code, diff, or pull request for assessment. Works on a single artifact, an artifact against a reference, a diff or PR, or two artifacts side by side.
Compare options and recommend a direction. Use for decision requests like "choose", "which option", "tradeoffs", "recommend", "should we", and option selection with criteria, risks, and reversibility.
Organize material into meaningful groups. Use for classification requests like "categorize", "group", "cluster", "sort", "taxonomy", "organize these", and grouping by criteria, priority, dependency, similarity, or abstraction level.
Explain any knowledge topic simply and accurately. Use for explanation requests like "explain X", "why/how/what is X?", concepts, science, definitions, code, design, architecture, and walkthroughs.
Investigate local repository, document, and attached-artifact context. Use for local investigation requests like "investigate", "find where", "understand this repo", "trace", and local-context research; do not use for web search.
Manage active work across people, agents, tasks, dependencies, blockers, and handoffs. Use for coordination requests like "manage this work", "lead this", "assign", "delegate", "track blockers", "status", "handoff", and multi-workstream execution.
| name | plan |
| description | Sequence work before execution. Use for planning requests like "break this down", "roadmap", "approach", "milestones", "how should we proceed", migration planning, rollout planning, and scoped next steps. |
| license | MIT |
| tags | ["plan","roadmap","sequencing"] |
| metadata | {"author":"Oleg Shulyakov","version":"1.1.0","source":"github.com/olegshulyakov/agent.md","catalog":"utility","category":"project-management"} |
Turn a goal into a practical sequence of work.
Scenario: Work needs sequencing Given the user asks how to proceed Then identify phases, dependencies, assumptions, risks, verification, and immediate next actions
Scenario: Execution is already active Given the primary need is managing live owners, blockers, or handoffs Then do not treat planning as the primary behavior And route the output toward coordination only when the user asks to manage ongoing work
Scenario: Durable documentation is optional Given the user has not requested durable files Then default to a conversational plan And create durable files only when the work clearly needs durable task documentation
Scenario: Goal is unclear Given the goal is not clear enough to plan reliably Then ask the one question that most affects scope And provide a provisional outline if useful
Scenario: Many unknowns exist Given too many unknowns prevent reliable sequencing Then split discovery from execution And identify what must be learned first
Scenario: Execution is already active Given the user asks about ongoing work Then switch the output toward status, blockers, and handoff only when the user asks to manage that work
Scenario: Output passes quality check Given a plan has been produced Then later steps do not require missing earlier outputs And validation or acceptance checks are included for non-trivial work And the plan is revised when new facts change scope, risk, or sequence
