skills.rest
alatyshau
alatyshauCOMMUNITY
Explore all skills by this author →
GitHub

planning

Generates implementation plans with completion criteria and commit-sized steps for complex changes.

Updated Nov 21, 2025
Search Tags:#planning#implementation plan#architecture decisions#completion criteria#workflow mode#topic file#commit steps
One-click install
npx skills add https://github.com/alatyshau/duet --skill planning-alatyshau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/alatyshau/duet/tree/main/packages/skills/modes/planning
Command: npx skills add https://github.com/alatyshau/duet --skill planning-alatyshau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex changes involving multiple files or architecture decisions often start without a clear plan, leading to broken code and lost context. This Skill structures the planning phase so every significant change begins with resolved open questions, explicit completion criteria, and commit-sized steps. ## Core Features & Use Cases - Open Questions Gate: Blocks plan writing until all open questions in the topic file reach resolved status. - Definition of Done First: Requires completion criteria before implementation steps, keeping plans traceable to the problem statement. - Commit-Sized Steps: Enforces one step equals one commit, with each step linked to its corresponding output specification. - Use Case: A user asks to add authentication to an API. The agent enters PLANNING mode, reads the topic file, resolves open questions, writes an implementation plan with criteria and steps, then waits for explicit approval before execution. ## Quick Start Ask the agent to switch to PLANNING mode and draft an implementation plan for your complex change before writing any code.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create an implementation plan before coding?▼

Enter PLANNING mode explicitly or let the agent detect complex work. The agent reads the topic file, resolves all open questions, defines completion criteria first, then writes commit-sized steps linked to output specifications.

When should planning mode be used instead of direct execution?▼

Use planning when a change touches multiple files, involves non-trivial architecture decisions, or risks breaking existing code. Simple fixes do not need a plan and can be executed directly.

What is the structure of a topic file in this workflow?▼

A topic file has six mandatory sections: motivation, links, narrative, open questions, outputs, and implementation plan. The plan contains a problem statement, completion criteria, and steps where each step equals one commit.

Can the agent start executing without explicit approval?▼

No. Transition from PLANNING to EXECUTE happens only after explicit permission such as a /next command or a clear yes. Interjections like ok or good are treated as feedback, not approval.

Why must open questions be resolved before writing a plan?▼

Unresolved questions mean the problem is not fully understood, so any plan would be premature. All questions must reach resolved status before outputs and implementation steps are written.

Related Skills

Explore More Software Engineering Skills→
datorresbdatorresb

ce-brainstorm

Guide structured brainstorming to surface requirements and document decisions.

Community
Advanced
porcupine-mdporcupine-md
11

iterating-to-completion

Prevent premature exit and infinite loops in multi-step AI task execution.

Official
Advanced
captaincontratcaptaincontrat

openspec-archive-change

Archives completed OpenSpec changes with metadata preservation using the openspec CLI.

Official
Advanced
zeveckzeveck

fix-issues

Coordinate batch bug-fix sprints across GitHub trackers and isolated worktrees.

Community
Advanced