mcpField
W
w-plan

w-plan

github.com/blockmaticAgent workflows1647 installsUpdated 4w ago
Repository

About w-plan

w-plan is a planning skill for developers and coding agents working in a repository. It structures exploration, goals, assumptions, and ordered tasks, while keeping planning separate from implementation, branching, and commits.

Key features

  1. 01Explore repository context and rules
  2. 02Define goals and constraints
  3. 03Record assumptions and non-goals
  4. 04Order tasks and identify dependencies
  5. 05Choose an output location

Use cases

  1. 01Plan a multi-file repository change
  2. 02Map tasks and dependencies before implementation
  3. 03Record assumptions and scope for a change

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blockmatic/basilic-skills --skill w-plan

After installing, type/w-planin Claude Code to confirm it loaded.

Bundled filesreferences/plan-output.md

Details

From the project README

Planning does not implement, branch, or commit. A single already-clear change uses /w-build. A blocking product gap uses /w-clarify. Stress-test a plan with /w-grill. Fog bigger than one session uses /w-wayfinder.

  1. Explore: if this turn has no reconciled exploration for the area, follow council steps 1–3, then continue.
  2. Goals: 3–7 bullets for scope, success, constraints, non-goals.
  3. Context: matching glob rule and skill, then topic MDX (or this repo’s docs path). Rules override skills. Inspect affected packages, README, scripts. Durable architecture: matching MDX/ADR. Generated outputs name an owning source; commands come from inspected scripts.
  4. Assumptions: 3–5 bullets. Defer product scope, secrets, and destructive ops.
  5. Tasks: ordered work with likely files and dependencies. Uncertain work first. Diagram only if relationships need one.
  6. Output: user’s path, else the repo’s existing plan file, else chat. Follow plan output.

Comments

Markdown supported