Schema Reference

Required fields

• intent: one clear outcome statement
• workflow: ordered list of execution steps
• success_checks: concrete checks for done/not-done

Recommended fields

• constraints: hard limits and non-negotiables
• preferences: style and tooling defaults
• failure_traps: known mistakes to avoid
• context: repo or domain assumptions

Shape guidelines

• Keep lists short and explicit.
• Prefer actionable statements over long prose.
• One pack should solve one level of scope well.

Validation checklist

• Every workflow step is testable.
• Every success check is observable.
• Constraints do not conflict with each other.
• File can be understood quickly by a new contributor.