shape

name	shape
description	Shape raw Gradient ideas into buildable context packets for docs, schemas, profiles, adapters, policy, context, or harness work. Trigger: /shape, /spec, /plan, /cp.
argument-hint	[idea|issue|backlog-item] [--spec-only|--design-only]

/shape

Shape the problem before selecting a mechanism. Gradient's common trap is building an adapter or profile tweak before naming the lifecycle stage and evidence requirement.

Context Packet

Include:

• Goal: user outcome, not implementation mechanism.
• Lifecycle stage strengthened.
• Non-goals and public-safe boundary.
• Authority order, usually decisions > architecture/module contracts > schema > profiles > exploratory docs.
• Repo anchors.
• Alternatives: at least minimal viable and ideal, with failure modes.
• Acceptance criteria and evidence.
• Implementation sequence.
• Risks and rollback.

Required Anchors

Use docs/architecture.md, docs/module-contracts.md, docs/decision-log.md, and the relevant profile/schema/doc. For Context work, also use docs/context-engine.md; for Policy, use docs/evals.md and docs/feedback-loop.md.

Output

A concise context packet that an implementer can execute without guessing.