planning-desklisted

Stand up and run a source-grounded planning desk under _meta/plans/ - deep build plans driven through a multi-round draft -> review -> fix -> reconcile loop over a tracker read through a pluggable adapter, plus analysis scripts for conformance, coverage, and reconciliation. Use whenever the user wants to plan a feature or epic before building, run a planning or backlog-grooming session, organize work under _meta/plans/, audit plan/tracker drift, triage a candidate list into MUST/DEFER/CUT, or set the desk up in a repo - even phrased as "plan this out", "groom the backlog", "scope this", "what should we cut", "run the scope hammer", or "get this repo's planning organized". It enforces deliverables/criteria/parallelism (never timelines) and grounds every claim in cited source. Not for writing the body of a tracked work item (task-authoring), not for creating a repo's meta-structure or filling audit gaps (mise-en-place-scaffold), and not the layout standard itself (repo-meta-structure).
hsb3/dotfiles-agents · ★ 0 · AI & Automation · score 70

Install: claude install-skill hsb3/dotfiles-agents

# Planning desk Turn fuzzy intent into build-ready, source-grounded plans on a local `_meta/plans/` desk, over a tracker read through a pluggable adapter. **The tracker holds STATE and the contract; the desk holds the build DETAIL.** ``` _meta/plans/ README.md # the live ACTIVE / ARCHIVED status index _config.md # THIS project's gates, tracker binding, canonical docs _utils/ # tracker.py loader + adapters/ + conformance, coverage, reconcile <slug>/plan.md # the build plan - and nothing else ``` ## Pick the mode | If the user wants to... | Mode | Read | | ----------------------------------------------- | ---------- | ----------------------- | | set up the desk in a repo that lacks one | **setup** | Setup, below | | produce a deep, source-grounded build plan | **plan** | `references/plan.md` | | run a multi-round planning session over a batch | **loop** | `references/loop.md` | | groom the backlog, audit drift, gate a wave | **govern** | `references/toolkit.md` | | cut a candidate list down to what ships now | **hammer** | Scope hammer, below | **For the body of a tracked work item - title, acceptance criteria, thresholds, scope - use the `task-authoring` skill**; its rules are not restated here. Desk absent? Set up first, then proceed. `references/entry-forms-and-milestones.md` carries the queue-entry forms and the milestone/gate vocabulary a boar