<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->

synthesize-spec

Run the spec-synthesis skill. Turn confirmed decisions into a publishable spec for docs/features or the configured tracker without re-interviewing settled choices.

This prompt follows Misbah Khursheed's Build Like This workflow: establish the user outcome and reasoning before generating implementation, then preserve that reasoning in contracts, boundaries, tests, and documentation.

Project identity and sources of truth

The repository where this prompt is installed is the host project being built. Build Like This is the engineering method used to build it, while mstack only installs and reconciles the method's resources. Do not mistake mstack or Build Like This for the host product unless project-owned sources explicitly say this repository develops mstack itself.

Project-owned docs/, decisions, executable code, and tests are the sources of truth. .mstack/templates/ are reference scaffolds that may be copied and adapted into project-owned documents; they are not requirements and do not replace docs/.

Treat the invocation arguments and current repository state as task input. Discover local instructions and relevant product, architecture, decision, contract, and test context before making material assumptions.

Method

1. Load the confirmed ledger and refuse to reopen settled decisions.
2. Synthesize outcome, stories, acceptance criteria, actors, failure states, and non-goals.
3. Confirm test seams with the user before publishing.
4. Publish to the configured tracker and/or feature doc; mark ready-for-agent only when criteria are testable.
5. Point the next step at ticket-graph or write-product-definition.

Deliverables

• Published spec path or issue with acceptance criteria.
• Readiness label and remaining decision gaps, if any.

Constraints

• Do not invent acceptance criteria.
• Do not embed implementation file trees unless prototyping was agreed.
• Do not skip planning-setup when the publish target is unclear.

Delegation and parallel safety

• For a material lifecycle task, the active lead must delegate at least one bounded specialist lane when subagents are available; prefer two or more concurrent lanes only when their evidence or file ownership is independent.
• The active lead owns acceptance criteria and final integration. Supporting agents must not recursively delegate unless explicitly promoted to lead a named lane.
• Give each delegate distinct inputs, outputs, and ownership. Serialize shared documents, contracts, schemas, migrations, deployments, external writes, and overlapping file edits.
• If subagents are unavailable, perform the named specialist passes sequentially and report the limitation; do not imply parallel verification.
• Delegation does not authorize outreach, paid resources, destructive changes, consequential external writes, or production deployment.

Finish with what changed or was decided, exact verification evidence, remaining risks, and the next decision only if one is genuinely required.

User arguments: $ARGUMENTS