Make some improvements to spec-related skills.

[vorporeal]

Description

The previous spec workflow could encourage redundant product specs for technically complex work, blur responsibility between selecting, writing, implementing, and validating specs, and leave approval boundaries implicit. That made it harder for humans and agents to align on an approved solution and keep the durable documentation synchronized with implementation.

This PR establishes a pragmatic workflow where spec-driven-implementation selects the smallest independently valuable artifact set: no spec, PRODUCT.md only, TECH.md only, or both. Direct writer skills honor and right-size requested documents, while implementation consumes the settled artifact set and all approved commitments regardless of which spec contains them.

The workflow now requires explicit human approval for the artifact path and drafted specs, requires implementation-blocking questions to be resolved or explicitly deferred, and requires approval before proposed material changes are persisted or acted upon. Validation also reads relevant approved sibling specs and distinguishes authoritative commitments from supporting context based on approval evidence rather than filenames alone.

Testing

• Ran multiple model-diverse council reviews, including cross-critique, and incorporated convergent findings and subsequent reviewer feedback.
• Ran local approval-boundary, material-change, responsibility-boundary, frontmatter, terminology, whitespace, and changed-file scope validation.
• Ran git diff --check.
• Skill/documentation-only change; no code tests were run.

Co-Authored-By: Oz oz-agent@warp.dev

[vorporeal]

• Make some improvements to spec-related skills. #30 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.