Skip to content

Add product-spec skill#3

Open
norbert-pap wants to merge 2 commits into
mainfrom
feature/product-spec-skill
Open

Add product-spec skill#3
norbert-pap wants to merge 2 commits into
mainfrom
feature/product-spec-skill

Conversation

@norbert-pap
Copy link
Copy Markdown
Owner

What

New product-spec skill for the claudebert workflow. Turns a stakeholder brain-dump into a single product handoff spec — one document that makes the work actionable for designer, engineer (and their coding agents), and PM without further meetings.

How it works

A tighter, output-shaped variant of superpowers:brainstorming — same explore → question → approaches → sectioned-review flow, but the terminal artifact is a fixed 8-section handoff format and process meta-commentary is stripped from the final doc.

  1. Explore the codebase first — before any questions, so the spec carries concrete real file pointers instead of abstractions
  2. Clarifying questions, one at a time, recommendation-led
  3. Propose 2–3 approaches for genuine architectural forks only
  4. Sectioned review with approval per section (visual mockups for spatial questions, terminal for conceptual)
  5. Write the spec to a file, commit it
  6. Push + open PR as the handoff

The 8-section format: Big picture · Lifecycle/core flow · UI intent · How it works · Edge cases · Test/deploy/instrumentation · Decisions log · Follow-ups.

Validation

evals/evals.json ships with 3 test prompts + assertions.

  • Artifact quality (iteration-1 benchmark): 100% assertion pass rate with-skill vs 16% baseline (no skill). With-skill runs consistently produced the exact 8-section format, ≥2 mermaid diagrams, populated decisions log, and ≥3 cited real file paths that exist in the repo.
  • Trigger accuracy: 19/20 on a 20-query eval set — 10/10 should-NOT-trigger queries correctly stayed quiet (no false-positives on adjacent skills: eng-review, prod-review, code-review, brainstorming, design-doc, qa), 9/10 should-trigger fired at 100%. The single miss references "the feature I described above" and only fails under stateless eval (no conversation context).

Notes

  • Scoped to only product-spec/ — the orchestrator (claudebert/SKILL.md) is not wired up in this PR to avoid tangling with other in-progress branch work. Add option B → /product-spec to the orchestrator separately.

🤖 Generated with Claude Code

norbert-pap and others added 2 commits May 14, 2026 14:33
Turns a stakeholder brain-dump into a single product handoff spec — one
document actionable for designer, engineer, and PM without further meetings.
Explores the codebase first so the spec carries concrete code pointers, runs
a question → approaches → sectioned-review flow, and ends with a committed
spec file and an open PR. A tighter, output-shaped variant of
superpowers:brainstorming with a fixed 8-section handoff format.

Includes evals/evals.json (3 test prompts + assertions). Iteration-1
benchmark: 100% assertion pass rate with-skill vs 16% baseline; trigger
accuracy 19/20 with zero false-positives on adjacent skills.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Step 5 now scans for an existing specs/docs/design/rfcs directory and
matches its convention (subdirectory grouping + filename pattern) before
falling back to docs/specs/. Eval runs all defaulted to docs/specs/ even
when the repo had its own spec home.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant