From cklph-architect
Pick the right engagement pattern — project, retainer, advisor, or fractional. Use when shaping a new engagement, restructuring an existing one, or deciding whether a "they want X" ask is really the wrong shape for the actual need.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cklph-architect:engagement-shapeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The shape of the engagement determines whether the work is sustainable. Pick wrong and you spend the engagement fighting the structure instead of doing the work. Four shapes cover most situations.
The shape of the engagement determines whether the work is sustainable. Pick wrong and you spend the engagement fighting the structure instead of doing the work. Four shapes cover most situations.
Project — fixed outcome, defined end date.
propose).scope).Retainer — ongoing access, capped scope per month.
Advisor — fractional strategic time, no execution.
Fractional — specific named role (Fractional CTO, Fractional Head of Sales, etc.) at a percentage of FTE.
Ask in this order:
When you're unsure, default to project. Projects have natural exit points. Retainers and fractionals are harder to graduate cleanly out of, so pick them deliberately.
Most engagement pain comes from the wrong shape:
price).When a shape isn't working, name it and re-shape — usually mid-engagement renewals are the right moment. "This started as a project but the work pattern is really a retainer; here's what that looks like and what it costs."
Pair with discover (the discovery surfaces which shape fits), scope (each shape scopes differently), propose (tiers can mix shapes — e.g. project + advisor retainer), price (shapes price differently), and position (peer-mode picks the right shape; vendor-mode takes whatever shape the client named).
npx claudepluginhub chykalophia/cklph-marketplace --plugin cklph-architectProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.