Pair with Spec Kit

Lamina structures product behavior. Spec Kit and Kiro structure engineering work. Use them in sequence — product contract first, engineering plan second.

Quick path

1. /lamina-init <domain> → domain charter
2. /lamina-design → implement.md (product contract)
3. Feed implement.md to Spec Kit → engineering plan
4. Your agent implements
5. /lamina-verify → confirm behavior matches contract

The split

Spec tools structure engineering work. Lamina structures what the product must do before engineering begins.

Recommended workflow

1. /lamina-init <domain>         → domain charter
2. /lamina-design <flow>         → implement.md (product contract)
3. Feed implement.md to Spec Kit → engineering plan
4. Your agent implements          → app source
5. /lamina-verify guest checkout at http://localhost:3000 → behavior verification

Why Lamina first?

Requirements often miss:

• Actor permission matrices
• State transition rules
• Edge case recovery paths
• Cross-actor interaction conflicts
• Dependency reachability between features

Lamina front-loads these into implement.md — a product contract Spec Kit can decompose into engineering tasks.

Handoff example

After /lamina-design, your implement.md might specify:

## Roles
- owner: full access, cannot demote self if last owner
- admin: manage members, send invites
- member: view only
 
## Invite flow
- pending → accepted → expired
- Last owner cannot demote themselves
 
## Edge cases
- Invite to existing member → show conflict error
- Expired invite → offer resend to admin only

Feed this to Spec Kit:

Create an implementation plan from this product contract in .lamina/runs/<run_id>/implement.md. Break into API endpoints, database schema, and test cases.

Spec Kit produces engineering tasks. Lamina verifies the final product matches the original contract.

When to use which

Next steps

• What is Lamina? — comparison with spec tools
• What to pair — broader pairing guide
• /lamina-design — create the product contract