planning

Plan software implementation phases using task_plan.md, findings.md, and progress.md files.

Updated May 2, 2026
One-click install
npx skills add https://github.com/iliaal/compound-engineering-plugin --skill planning-iliaal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/iliaal/compound-engineering-plugin/tree/main/distillery/generated-skills/planning
Command: npx skills add https://github.com/iliaal/compound-engineering-plugin --skill planning-iliaal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill tackles the challenge of managing complex software development tasks by providing a structured, file-based approach to planning, tracking progress, and documenting findings, preventing information loss and ensuring clarity.

Core Features & Use Cases

  • Phased Implementation Planning: Break down large features into manageable phases with defined tasks, scope, and verification steps.
  • Persistent Documentation: Utilizes task_plan.md, findings.md, and progress.md for durable record-keeping of decisions, research, and execution status.
  • Context Management: Enforces rules for updating and referencing planning files to maintain an accurate understanding of the project state within the AI's context window.
  • Use Case: When starting a new, multi-file feature, use this Skill to proactively create a task_plan.md outlining the approach, scope, and initial phases, ensuring all team members (including the AI) are aligned before coding begins.

Quick Start

Use the planning skill to create a new implementation plan for the 'user authentication' feature.

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure complex software development tasks into actionable phases?

To structure complex software development tasks, break down large features into manageable phases with defined tasks, scope, and verification steps using file-based persistence. This approach prevents information loss and ensures clarity for multi-file changes or new feature development.

What is the best way to maintain project context during multi-file changes?

The best way to maintain project context during multi-file changes is using persistent documentation files like task_plan.md, findings.md, and progress.md. This enforces context management rules, ensuring an accurate understanding of the project state within the AI's context window.

When do I need a dedicated implementation plan for software project management?

You need a dedicated implementation plan for software project management when a complex task requires more than five tool calls, involves multi-file changes, or entails new feature development. This prevents information loss and ensures iterative refinement.

How does file-based task management work for software implementation?

File-based task management works by utilizing task_plan.md, findings.md, and progress.md for durable record-keeping of decisions, research, and execution status. It enforces rules for updating and referencing planning files to maintain an accurate project state.

Can I use markdown files for tracking progress in complex software development?

Yes, you can use markdown files for tracking progress in complex software development. Persistent documentation files like progress.md and findings.md provide durable record-keeping of execution status and research, preventing information loss across iterative refinement phases.

What are the limitations of using file-based documentation for project management?

A limitation of file-based documentation for project management is the strict requirement to enforce rules for updating and referencing planning files. Without enforcing context safety and limiting phase scope, the project state understanding within the context window may degrade.