How does it compares to openspec or other spec driven frameworks ? #285

I had some early experience with Spec-Kit. In comparison, this seems more lightweight and agile.

I don't think openspec is locking the developer in specific process, unlike the methods above

OpenSpec's current README supports that point: it keeps proposal, specs, design and tasks for each change, while allowing you to revise artifacts without rigid phase gates.

Matt's repo provides editable, composable skills for interviewing, domain modeling, TDD and implementation. There is overlap: /to-spec publishes a spec to your configured tracker, and /to-tickets breaks work down, so those steps cover some of the same ground as OpenSpec's proposal and task generation.

If OpenSpec already works for you, keep its artifacts as the authoritative plan. Use /grill-with-docs to clarify decisions, carry those decisions into your OpenSpec proposal/design, then continue its implementation and archive workflow. You can adopt selected skills without maintaining a second competing set of specs and tickets. That handoff is something you arrange explicitly.