plan-writing

Generate task plans with dependencies and verification criteria for software projects.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/lchenrique/politron-ide --skill plan-writing-lchenrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/lchenrique/politron-ide/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/lchenrique/politron-ide --skill plan-writing-lchenrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined framework for breaking work into small, verifiable tasks with dependencies and clear acceptance criteria, enabling reliable project execution.

Core Features & Use Cases

  • Task Breakdown: generate 2-5 minute tasks with independent outcomes.
  • Verification Focus: explicit criteria to verify completion.
  • Dynamic Planning: adapt task names and order based on project type (NEW, FEATURE ADDITION, BUG FIX).
  • Use Case: plan a feature implementation with phases, tasks, and validation steps.

Quick Start

Run the plan-writing skill to generate a task plan for implementing a new feature.

Frequently Asked Questions about plan-writing

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

FAQPage Schema
How do I break down a software feature into actionable tasks for agile project management?

To break down a software feature for agile project management, generate 2-5 minute tasks with independent outcomes. This structured framework ensures each task has clear dependencies and explicit verification criteria to validate completion.

What is the best way to write a task plan with verification criteria for a refactoring project?

Writing a task plan with verification criteria for refactoring requires defining explicit, verifiable outcomes for each small task. This approach enforces project-specific task naming and concise, task-level documentation to ensure reliable execution.

Can I adapt task planning and naming conventions for different project types like bug fixes or new features?

Task planning can adapt dynamically to project types like NEW, FEATURE ADDITION, or BUG FIX. The framework adjusts task names and ordering based on the specific project context, enabling consistent planning outcomes across any software engineering work.

Do I need any external runtimes or dependencies to generate multi-step software task plans?

Generating multi-step software task plans requires no external runtimes or dependencies. The framework operates entirely within a local text-based workflow, needing only your project details to structure phases, tasks, and validation steps.

How does dynamic task planning handle dependencies and task ordering during feature implementation?

Dynamic task planning handles dependencies by mapping small, verifiable tasks and their order based on project type. It structures feature implementation into sequential phases with clear validation steps, ensuring reliable project execution.