ワンクリックで
skill-planning-format
Standards for Development Plans (PLAN.md) and Detailed Task Descriptions (TASK.md).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Standards for Development Plans (PLAN.md) and Detailed Task Descriptions (TASK.md).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | skill-planning-format |
| description | Standards for Development Plans (PLAN.md) and Detailed Task Descriptions (TASK.md). |
| tier | 1 |
| version | 1.1 |
Purpose: Defines the rigid structure for planning documents effectively.
STOP if you are thinking:
task-*.md file for tracking.docs/PLAN.md)The Main Plan acts as the "Table of Contents" for the feature.
[!TIP] Use the template at
assets/templates/plan_md_template.md.
For each task in the plan, you must create a separate file: docs/tasks/task-{ID}-{SubID}-{slug}.md.
[!TIP] Use the template at
assets/templates/task_md_template.md.
| Agent Excuse | Reality / Counter-Argument |
|---|---|
| "I don't know the implementation details yet" | That is why you are in PLANNING mode. Research until you know. |
| "Writing 5 files takes too long" | Fixing a disorganized codebase takes 10x longer. |
docs/PLAN.md file — general development plan with task sequence.docs/tasks/task-{ID}-{SubID}-{Slug}.md files — detailed descriptions of each task.[Link](docs/tasks/file.md)), never absolute.assets/templates/: Standard markdown templates.examples/: Real-world planning examples.Use when decomposing tasks into parallel sub-tasks or spawning sub-agents. Vendor-agnostic core; load a per-vendor reference for concrete tool names, directory conventions, and invocation syntax.
Use when performing Verification-Driven Development with adversarial approach. Actively challenge assumptions and find weak spots.
Use when performing VDD adversarial review with an opt-in sarcastic, provocative delivery style — a stylistic skin over vdd-adversarial mechanics (exhaustive reporting + objective bar).
Performance critic in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing OWASP security critique in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing security vulnerability assessment (OWASP, secrets, dependencies, IaC, LLM, API, MCP/agentic) or when "thinking like a hacker" to find exploits.