work-item-planning

1作業=1ディレクトリ(docs/<work_item>/)で、implementedplan.md と tasks.md を作る手順とテンプレ。

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 2, 2026⬇️1downloads

When & Why to Use This Skill

The work-item-planning skill provides a structured framework for transforming high-level objectives into actionable implementation plans and granular task lists. By enforcing a standardized directory structure (docs/<work_item>/) and utilizing templates for 'implementedplan.md' and 'tasks.md', it ensures that every project phase has clear completion criteria and a well-defined roadmap, significantly reducing ambiguity in execution.

Use Cases

  • Software Development Planning: Automatically generating a structured implementation roadmap and task breakdown for new features or bug fixes to ensure technical alignment.
  • Standardized Workflow Documentation: Establishing a consistent project history by organizing work items into versioned directories with mandatory planning and task files.
  • AI Agent Task Orchestration: Providing a reliable template for AI agents to 'think' and plan their steps before execution, preventing premature implementation and ensuring all 'Definition of Done' criteria are met.
  • Team Collaboration: Improving handoffs between team members by providing a clear, document-based record of what was planned versus what tasks are required for completion.
namework-item-planning
description|

目的

planca が短時間で「実装可能な計画」と「完了条件つきタスク」を作れるようにする。

手順

  1. work_item を決める(YYYY-MM-DD_<short-slug>_vN)
  2. docs/<work_item>/ を前提に、次の2ファイルを作成する
    • implementedplan.md
    • tasks.md
  3. tasks は「完了条件」が曖昧にならないように書く

implementedplan.md テンプレ

templates/implementedplan.template.md を参照。

tasks.md テンプレ

templates/tasks.template.md を参照。

よくある落とし穴

  • 「タスクの完了条件」が書かれていない
  • 実装に踏み込みすぎて、判断が必要な点を oca に返さない