aiskillstore/marketplace / skills/0xmsc/plan
plan
VerifiedGuidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a non-trivial task or when you need to align on a complex implementation strategy.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 946 B |
| references/principles.md | markdown | 1.4 KB |
| skill-report.json | config | 8.2 KB |
skill-report.json
View on GitHub{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-07-06T01:05:12.813Z",
"slug": "0xmsc-plan",
"source_url": "https://github.com/0xmsc/coding_assistant/tree/master/src/coding_assistant/skills/plan",
"source_ref": "master",
"model": "codex",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "1916911764943fb3eea72dd3d688659754a40f5bd27915e492ad1263b6ec567c",
"tree_hash": "82a1aaa839fc63ae86746b9b7fa18e9e1b4a4d7d28ee616433feaea52b525461",
"provenance": {
"model_requested": "gpt-5.5:high",
"model_effective": "codex:gpt-5.5:high",
"fallback_chain": [
{
"agent": "codex",
"model": "gpt-5.5",
"effort": "high",
"outcome": "success"
}
],
"analysis_version": "3.0.0"
}
},
"skill": {
"name": "plan",
"description": "Planning guidance for complex coding tasks that need exploration, user alignment, staged implementation, and clear verification steps.",
"summary": "Plan complex coding work before making changes.",
"icon": "📦",
"version": "1.0.0",
"author": "0xmsc",
"license": "MIT",
"category": "productivity",
"tags": [
"planning",
"workflow",
"code-review",
"implementation"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": []
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"analysis_status": "ok",
"summary": "The only static finding is a false positive. The referenced line promotes iterative planning and contains no system reconnaissance, command execution, or data collection behavior.",
"remediation": [],
"risk_factor_evidence": [],
"static_findings": [
{
"id": "blocker:references/principles.md:9:system-reconnaissance",
"category": "blocker",
"severity": "low",
"pattern": "System reconnaissance",
"file": "references/principles.md",
"line_start": 9,
"line_end": 9,
"snippet": "Avoid spending hours on a perfect plan for a massive task. Instead:"
}
],
"finding_verdicts": [
{
"id": "blocker:references/principles.md:9:system-reconnaissance",
"verdict": "false_positive",
"confidence": 0.96,
"reason": "Line 9 advises avoiding overlarge plans and working in smaller milestones. It does not request system reconnaissance, command execution, or data collection."
}
],
"semantic_findings": [],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 2,
"total_lines": 56,
"audit_model": "codex",
"audited_at": "2026-07-06T01:05:12.813Z",
"agent_auto_install_policy": "allowed",
"manual_install_policy": "allowed"
},
"content": {
"user_title": "Plan Complex Coding Tasks",
"value_statement": "Complex coding requests can drift when work begins too soon. This skill helps Claude and Codex create staged plans with questions and verification.",
"seo_keywords": [
"Claude",
"Codex",
"Claude Code",
"AI planning skill",
"coding workflow",
"implementation planning",
"task decomposition",
"verification planning",
"developer productivity"
],
"actual_capabilities": [
"Guides codebase exploration before planning.",
"Structures plans with objective, approach, steps, and verification.",
"Prompts the assistant to ask clarifying questions with proposed answers.",
"Encourages user approval before implementation starts.",
"Promotes milestone planning for large tasks.",
"Highlights risky changes and verification steps."
],
"limitations": [
"Does not implement code without separate execution by the assistant.",
"Does not replace project-specific architectural judgment.",
"Requires clear user approval for the intended workflow.",
"Does not provide automated tests or validation by itself."
],
"use_cases": [
{
"title": "Plan a Multi-File Change",
"description": "Break a broad implementation request into scoped steps, risks, and checks before editing files.",
"target_user": "Software engineer"
},
{
"title": "Align on Ambiguous Requirements",
"description": "Turn unclear product or technical requests into questions, assumptions, and proposed answers.",
"target_user": "Product manager"
},
{
"title": "Stage Risky Refactors",
"description": "Separate a large refactor into safe milestones with approval and verification at each stage.",
"target_user": "Technical lead"
}
],
"prompt_templates": [
{
"title": "Basic Plan",
"prompt": "Use the plan skill to outline the objective, approach, steps, and verification for this task.",
"scenario": "A beginner wants a simple implementation plan before work starts."
},
{
"title": "Clarify First",
"prompt": "Use the plan skill and include clarifying questions with proposed answers before implementation.",
"scenario": "A request has missing details or several valid directions."
},
{
"title": "Milestone Plan",
"prompt": "Use the plan skill to split this project into manageable milestones with approval points.",
"scenario": "A larger change needs staged delivery and feedback."
},
{
"title": "Risk-Aware Plan",
"prompt": "Use the plan skill to identify risky changes, safer alternatives, and verification steps.",
"scenario": "An advanced user wants a plan for shared code or production-sensitive changes."
}
],
"output_examples": [
{
"input": "Plan a feature that adds saved searches to an existing dashboard.",
"output": "A concise plan with exploration steps, key assumptions, three clarifying questions, implementation milestones, and validation checks."
},
{
"input": "Plan a refactor of authentication middleware across several services.",
"output": "A staged refactor plan that calls out shared-library risk, approval checkpoints, rollback considerations, and targeted tests."
}
],
"best_practices": [
"Use this skill before complex edits or unclear implementation requests.",
"Answer the clarifying questions before asking the assistant to implement.",
"Keep the plan focused on the next useful milestone."
],
"anti_patterns": [
"Using the skill for trivial one-line changes.",
"Treating the first plan as final when new facts appear.",
"Skipping verification steps for risky or shared code changes."
],
"faq": [
{
"question": "What does this skill help with?",
"answer": "It helps Claude, Codex, and Claude Code create clear plans before complex coding work begins."
},
{
"question": "Does it make code changes?",
"answer": "No. It guides planning and approval before a separate implementation step."
},
{
"question": "When should I use it?",
"answer": "Use it when a task has multiple files, unclear requirements, or meaningful implementation risk."
},
{
"question": "What should a good plan include?",
"answer": "A good plan includes the objective, approach, steps, clarifying questions, risks, and verification."
},
{
"question": "Can it help with refactoring?",
"answer": "Yes. It is useful for breaking refactors into safer milestones with approval points."
},
{
"question": "Is it suitable for beginners?",
"answer": "Yes. It provides a clear structure that helps beginners understand and review proposed work."
}
]
},
"file_structure": [
{
"name": "references",
"type": "dir",
"path": "references",
"children": [
{
"name": "principles.md",
"type": "file",
"path": "references/principles.md",
"lines": 30
}
]
},
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 26
}
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |