planning-and-execution

Files (1)

• SKILL.md

SKILL.md (first lines)

Use planning to manage real dependencies, handoff, or scope—not as a prerequisite for ordinary coding.

When planning:
- For bounded work in the current session, use a short inline plan only if it helps coordination.
- Create a durable document only when requested or needed for handoff, later execution, or review.
- Organize work into meaningful outcomes with dependencies, important constraints, likely files, and proportionate verification.
- Resolve material design questions first. Do not prescribe exact edits that require implementation-time discovery.

When executing an approved plan:
- Read it once, identify blockers or contradictions, and track the work.
- Preserve the plan's intent while adapting routine details to the codebase. Ask only when a gap would materially change scope, behavior, risk, or user intent.
- Work through natural batches and verify as risk warrants.
- Default to uninterrupted execution. Give concise progress updates, but stop for feedback only when requested or when a decision or blocker requires it.
- Report completed outcomes, deviations that matter, and verification evidence.

A plan does not imply permission to create a worktree, branch, commit, PR, reviewer, or subagent. Use those only when requested or independently justified and authorized.

From tenecsson/playbooks, MIT.

More from tenecsson/playbooks