Skip to content
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.

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).

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.