Skip to content

abrahamferga/shape

v0.1.0MIT

The design loop: decide the SHAPE once, against the platform rather than from scratch. Which modules and manifests, which tools and the permission gating each, which writes are approval-gated, which connectors and plans, which host seams — recorded in ARCH.md plus ADRs for every non-default choice, with the backlog marked Ready. Enable to design, then disable for the long delivery phase.

GitHub
design-product

Turn PLAN.md into ARCH.md plus DECISIONS.md for a product on the Plenipo platform, where architecture is a delta against a stack that is already chosen: the module boundary and manifest, the tool surface with its permission strings and approval flags, the tab surface, the module DbContext and its per-entity query filters, the host seams used, connectors, and the plan model — then mark each backlog item Ready once its shape is settled. USE FOR: writing ARCH.md and the ADRs before any code exists, deciding what belongs in the module versus a host seam, gating every write, drawing the module's component view. DO NOT USE FOR: deciding what the product does or ordering its epics (/define:plan-product), or authoring module code member by member (/deliver:plenipo-module-sdk).