home / skills / codingheader / myskills / 0xmsc-plan

0xmsc-plan skill

safe

This skill guides iterative task planning before implementation, detailing objectives, approach, steps, verification, and clarifying questions to align with

npx playbooks add skill codingheader/myskills --skill 0xmsc-plan

Review the files below or copy the command above to add this skill to your agents.

Files (3)

SKILL.md

946 B

---
name: plan
description: Guidelines for iteratively planning tasks and changes before implementation. Use this when the user requests a non-trivial task or when you need to align on a complex implementation strategy.
---

# Task Planning

## Workflow
1. **Gather Information**: Explore codebase and list dependencies.
2. **Draft Plan**:
   - **Objective**: Goal of the task.
   - **Approach**: High-level strategy.
   - **Steps**: Sequential actions.
   - **Verification**: How to prove it works.
3. **Clarify**: Include **at least 3 clarifying questions** with proposed answers.
4. **Approve**: Wait for user "go ahead" (empty response = approval).
5. **Implement**: Execute only after approval.

## Principles
- **Zero-Impact**: Do not modify files during planning.
- **Iterative**: Refine based on feedback.
- **Concise**: Keep plans readable and progress tracked via TODOs.

## References
- [Planning Principles](references/principles.md)

Overview

This skill provides a disciplined, iterative planning process for non-trivial tasks or changes before any implementation begins. It produces a clear objective, high-level approach, ordered steps, verification criteria, and at least three clarifying questions with proposed answers. The goal is to align expectations, minimize risk, and avoid touching code during planning.

How this skill works

I inspect the request and any available project context, list relevant dependencies and areas of impact, and draft a compact plan that includes objective, approach, sequential steps, and verification. The plan always contains at least three clarifying questions with suggested answers to uncover assumptions and drive an approval decision. I do not modify files during planning and iterate the draft based on your feedback until you explicitly approve.

When to use it

When a task or feature has multiple implementation paths or unknown dependencies
Before making architecture, API, or large refactor decisions
When coordinating work across teams or contributors
When you need explicit verification and rollback criteria
Whenever risk should be minimized before coding starts

Best practices

Gather key context first: repo layout, dependencies, tests, and CI
Keep the plan concise: objective, approach, steps, verification, and TODO markers
Always include at least three clarifying questions with proposed answers
Prefer zero-impact investigation—do not edit files during planning
Iterate plans based on feedback and wait for explicit approval before implementing

Example use cases

Plan a migration of a database schema that affects multiple services
Design an API change with backward compatibility and rollout steps
Scope a large refactor by breaking it into safe, verifiable increments
Coordinate feature delivery involving frontend, backend, and infra changes
Define verification steps for performance optimizations and how to revert

FAQ

How many clarifying questions will you include?

At least three, each with a proposed answer to surface assumptions and decision points.

Will you make any code changes during planning?

No. Planning follows a zero-impact rule—no files are modified until you approve the plan.