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.

synthesize-spec

Turn research/<industry>.md into SPEC.md — the one-sentence framing, jobs to be done, personas and their authority tiers, the must-have / differentiator / out-of-scope capability split, an RBAC model of dotted action-noun permissions, regulatory constraints, and observable success metrics. Its defining move is binding every capability to a named Plenipo seam — module tool (approval-gated if it writes), tab, connector, background job, module endpoint, host seam — and deleting outright anything the platform already supplies. USE FOR: writing or re-scoping a product spec, cutting v1 down to what ships, sketching the shipped role baselines. DO NOT USE FOR: the competitive landscape (../research-industry), epics and build order (../plan-product), or technology, layout and data-model decisions (/shape:design-product).

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.