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.

research-industry

Competitive research on one chosen industry, written to research/<industry>.md: who the leading commercial vendors are, a capability comparison matrix built only from sources actually opened, the recurring UX patterns buyers already expect, the regulatory obligations that shape the build, a one-to-one map of the industry's table stakes onto what Plenipo already delivers, an explicit list of what it does not, and a must-have / differentiator / out-of-scope split. This is the artifact the spec is written from. USE FOR: mapping a vendor landscape from cold, separating table stakes from differentiators, sourcing the compliance obligations that constrain v1, refreshing stale research. DO NOT USE FOR: turning the findings into a specification (../synthesize-spec) or deciding which vertical to enter in the first place (/scout:find-industry).

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.