skills.rest
tae0y
tae0yCOMMUNITY
Explore all skills by this author →
GitHub

planning

Plan software work in small, known-good increments with one-commit-per-step discipline.

14|Updated Feb 15, 2026
Search Tags:#workflow#planning#project-management#worklog#increment#localdocs
One-click install
npx skills add https://github.com/tae0y/python-project-template --skill planning-tae0y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/tae0y/python-project-template/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/tae0y/python-project-template --skill planning-tae0y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning work in small, known-good increments helps teams keep the codebase healthy, reduce risk, and create clear checkpoints before implementing significant changes.

Core Features & Use Cases

  • Incremental planning: Break work into small, auditable steps that can be reviewed and approved.
  • Documentation & learning alignment: Use localdocs files to track goals, progress, and lessons learned.
  • Progress governance: Maintain a transparent worklog (todo/doing/done) to coordinate teams and reviews.

Quick Start

Create localdocs/plan.<topic>.md to outline the feature and obtain explicit plan approval before starting execution.

Frequently Asked Questions about planning

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

FAQPage Schema
What is incremental planning for software projects?▼

Incremental planning breaks work into small, auditable steps to keep the codebase deployable. It creates clear checkpoints, reduces risk, and requires plan approval before execution begins.

How do I track project progress using a worklog?▼

You track project progress using a transparent worklog that categorizes tasks into todo, doing, and done states. This coordinates teams and reviews throughout the workflow.

How do I enforce one-commit-per-step discipline in project management?▼

You enforce one-commit-per-step discipline by planning work in small, known-good increments and requiring plan approvals. This ensures the codebase remains in a deployable state.

Does incremental planning require explicit plan approval before coding?▼

Yes, incremental planning requires explicit plan approval before execution. You must outline the feature and obtain approval to maintain codebase health and create clear checkpoints.

When do I need localdocs files for planning a feature?▼

You need localdocs files during early planning phases to outline features, track goals, and capture lessons learned. They provide documentation alignment and worklog tracking before execution.

Related Skills

Explore More Product & Management Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
taewook486taewook486

worklog

Transition tasks between todo, doing, and done states in worklog files.

Community
Basic
heman1033p-createheman1033p-create

rrr

Generates session retrospectives with AI diary entries and lessons learned from git history.

Community
Intermediate
tae0ytae0y
14

status

Consolidate worklog, plan, and implementation status into a project health snapshot.

Community
Intermediate