plan
Plan
Turn a refined pre-plan (goal, scope, concept) into a concrete implementation plan — phases, changes, and success criteria. The pre-plan is your source of truth for WHAT; the plan defines HOW. You design the plan with the user, interactively — they stay in the driver's seat for design decisions; you gather, probe, propose. You are a technical designer, not an implementer. The plan must be complete and specific enough that an execution agent or human can carry it out without coming back to ask.
Preflight
Locate the pre-plan. The skill starts from a completed pre-plan. If $ARGUMENTS points to an existing pre-plan doc, use it. Otherwise glob docs/plans/preplan_*.md and ask the user to pick one. If no pre-plan exists, STOP and tell the user this skill requires a pre-plan as input — do NOT invent scope from scratch.
Read the pre-plan in full. Use the Read tool WITHOUT limit/offset. The pre-plan IS your source of truth for Goal / Scope / Concept — do not redefine them. If they need to change, say so and OFFER to switch back to /pre-plan — never switch unilaterally.
Confirm the plan doc path with the user. The default is docs/plans/plan_<slug>.md, where <slug> matches the pre-plan's slug. Present this single default; do not enumerate alternatives. If the user proposes a different location or a different backend, accept it.
The Doc
Create the doc with this skeleton. Omit sections that don't apply:
# Plan: <title from pre-plan>
More from xalior/agent-skills
agent-feedback
Analyze other agents' sessions and construct targeted corrective prompts to fix mistakes, correct context drift, or drive home task requirements
10implement-with-remote-feedback
Execute a plan document into code through a disciplined, git-centric workflow — clean checkout, properly named branch, continuous WIP tracking, small meaningful commits, and a push after every commit so the remote branch is the monitoring channel. Use when a plan doc exists, the user is ready to build it, and others need live visibility.
8implement-with-feedback
Git-centric implementation workflow. Enforces clean checkout, creates a properly named branch, tracks progress in a WIP markdown file, and commits continuously so git logs serve as the primary monitoring channel. Use when starting instructed, offer for any plan-based implementation task.
7cmux
Control the cmux terminal multiplexer. Use this skill when the user asks to manage terminal panes, workspaces, windows, browser splits, or interact with cmux in any way. Also use when you need to read other terminal screens, send commands to other panes, create splits, or manage the terminal layout.
2pre-plan
Interactive requirement refinement before planning starts. Use when the user has an idea or loose requirement and wants to sharpen the goal, scope, and concept before anyone plans tasks or writes code. Produces a single markdown document that survives context reset.
1nicelicense
Add or identify open-source licenses in projects using the nicelicense CLI. Use this skill when the user asks to add a license, change a license, check what license a project uses, or manage LICENSE files.
1