Skip to content

abrahamferga/define

v0.1.0MIT

The definition loop: decide WHAT to build. Competitive industry research -> product spec (SPEC.md) -> plan with the module split, tool inventory and RBAC model (PLAN.md) -> the feature backlog published as GitHub issues on a project board. Enable at kickoff; disable once the backlog is published so its descriptions stop costing context.

sync-backlog

Project PLAN.md into GitHub as the system of record: epic and feature issues upserted by a hidden marker so a re-run never fans out duplicates, features linked under their epic as sub-issues, and every card on the Projects v2 board in Backlog with its build order. Also reaps the gap the predecessor left open — an issue whose capability was deleted from the plan is detected and closed or escalated, instead of sitting Ready waiting for someone to build it. USE FOR: publishing a finished plan to issues plus a board, re-syncing after the plan changed, finding orphaned issues. DO NOT USE FOR: authoring the plan (../plan-product), creating the repo or the board (/deliver:scaffold-product), moving cards out of Backlog (/shape:design-product), implementing an issue (/deliver:work-next-issue).

License
MIT
Read SKILL.md at the source

Pinned to revision a2ee8094fc23, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.