Companion to the generate-feature-docs skill (skill #1). While skill #1 verifies that handles (config keys, endpoints, headers, error variants) referenced in a spec exist in crates/, it does not verify that the behavior of the code matches what the spec describes.
Skill #2 closes that gap. It consumes the same structured outline that skill #1 produces in stage 1 and adds behavior verification on top. Output is a roadmap-style "planned for later" list with rough engineering estimates: which spec promises are fully shipped, which are partial, and which are missing.
Reference: docs/superpowers/specs/drafts/2026-04-28-generate-feature-docs-skill-design.md Section 13 (Out of scope, deferred to skill #2).
Optional v2 enhancement
Consume GitHub PR review comments via gh pr view <implemented_in> --comments to incorporate post-spec engineering decisions that never made it back into the spec body. This is an optional follow-up after the core skill #2 lands; not required for v1.
Companion to the
generate-feature-docsskill (skill #1). While skill #1 verifies that handles (config keys, endpoints, headers, error variants) referenced in a spec exist incrates/, it does not verify that the behavior of the code matches what the spec describes.Skill #2 closes that gap. It consumes the same structured outline that skill #1 produces in stage 1 and adds behavior verification on top. Output is a roadmap-style "planned for later" list with rough engineering estimates: which spec promises are fully shipped, which are partial, and which are missing.
Reference:
docs/superpowers/specs/drafts/2026-04-28-generate-feature-docs-skill-design.mdSection 13 (Out of scope, deferred to skill #2).Optional v2 enhancement
Consume GitHub PR review comments via
gh pr view <implemented_in> --commentsto incorporate post-spec engineering decisions that never made it back into the spec body. This is an optional follow-up after the core skill #2 lands; not required for v1.