skills.rest
TimeKast
TimeKastOFFICIAL
Explore all skills by this author →
WebsiteGitHub

plan-writing

Convert vague objectives into structured task plans with verification criteria.

Updated May 19, 2026
Search Tags:#refactoring#task planning#dependency mapping#verification criteria#project root#software change
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill plan-writing-timekast
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill plan-writing-timekast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of unclear, risky work planning by turning an objective into small, independently verifiable tasks with explicit verification criteria.

Core Features & Use Cases

  • Small, focused tasks: keeps each step short (2–5 minutes) with one clear outcome.
  • Verification criteria baked in: defines how to confirm completion via checks/tests and expected outputs.
  • Dependency-aware ordering: highlights critical path and identifies what can run in parallel.
  • Correct plan placement rules: enforces dynamic naming as {task-slug}.md in the project root and prevents writing plans into hidden/temp folders.
  • No template lock-in: produces unique plans per task rather than copying a fixed structure.

Quick Start

Ask the AI to create a plan for your next feature or refactor, including specific verification steps, with the plan saved as a {task-slug}.md file in the project root.

Frequently Asked Questions about plan-writing

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

FAQPage Schema
How do I break a software change into small, independently verifiable tasks?▼

Task planning for refactoring works by mapping dependencies to highlight the critical path and identify parallelizable work. This ensures safe execution by ordering steps logically and baking verification criteria directly into the plan's confirmation structure.

How do I map dependencies and critical paths for a refactoring plan?▼

Task planning for refactoring works by mapping dependencies to highlight the critical path and identify parallelizable work. This ensures safe execution by ordering steps logically and baking verification criteria directly into the plan's confirmation structure.

What is the best way to structure a plan with explicit verification criteria?▼

Yes, plan files are saved dynamically as `{task-slug}.md` directly in the project root. This placement rule prevents writing plans into hidden or temporary folders, keeping software change documentation accessible and organized.

Does the plan-writing system save task plans to a specific project directory?▼

Yes, plan files are saved dynamically as `{task-slug}.md` directly in the project root. This placement rule prevents writing plans into hidden or temporary folders, keeping software change documentation accessible and organized.

Can I use a fixed template for my software change task plans?▼

No, you cannot use a fixed template because the system produces unique plans per task rather than copying a fixed structure. It dynamically generates plans tailored to the specific objective, dependencies, and required verification steps.

Related Skills

Explore More Software Engineering Skills→
Festo-WampambaFesto-Wampamba

custom-goals

Transform vague objectives into verified task plans with explicit completion criteria.

Community
Intermediate
alex-tgkalex-tgk
1

Verification Before Completion

Execute verification commands to validate tests, lint, and builds before commits.

Community
Advanced
aurora-atomsaurora-atoms

implementation-plan

Generate structured implementation plans with dependency graphs and validation checkpoints.

Community
Advanced
AnastasiyaWAnastasiyaW
140

plan-to-tickets

Decompose project plans into Markdown tickets with acceptance criteria.

Community
Intermediate