borghei/Claude-Skills / project-management/discovery/ai-prototyping
ai-prototyping
UnverifiedIdea to AI-generated prototype to customer validation to engineering handoff. Use when deciding prototype vs spec, choosing fidelity, briefing AI prototyping tools, testing with users, or handing a prototype to engineering.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.2 KB |
| assets/handoff_complete.json | config | 3.5 KB |
| assets/handoff_incomplete.json | config | 867 B |
| assets/handoff_template.md | markdown | 1.7 KB |
| assets/hypotheses_sample.json | config | 2.0 KB |
| assets/hypotheses_untestable.json | config | 1.2 KB |
| assets/prototype_brief_template.md | markdown | 2.7 KB |
| examples/mobile-expense-approvals.md | markdown | 6.1 KB |
| references/prototype-decision-guide.md | markdown | 8.0 KB |
| references/testing-handoff-governance.md | markdown | 8.9 KB |
| scripts/prototype_handoff_checker.py | script | 9.5 KB |
| scripts/prototype_plan.py | script | 10.2 KB |
assets/handoff_template.md
View on GitHub# Prototype Handoff: <initiative name>
<!-- Fill every section. Validate with:
python3 scripts/prototype_handoff_checker.py --input this-file.md
Headings are matched by keyword, so keep the words shown in each heading. -->
**Owner (PM):** <name> **Engineering lead:** <name> **Date:** <YYYY-MM-DD>
## Prototype link
- <URL to the prototype, version or commit>
## Disposition
- <throwaway | starting point> - <one sentence on what engineering may reuse>
## Problem and users
- <Who has the problem, what it costs them, and the evidence (interviews, tickets, data)>
## Success metrics
- <Metric> - baseline <value>, target <value>, window <period>
## Validated findings
- <Hypothesis> - <n> participants - threshold <pre-set bar> - result <what happened> - <validated | invalidated | open>
## Acceptance criteria
- Given <context>, when <action>, then <observable, measurable result>
## Non-goals
- <What this build will explicitly not do, even though the prototype showed it>
## Constraints
- <Technical, legal, budget, timeline>
## Risks and open questions
- <Risk, owner, how and when it gets retired>
## Throwaway list (what the prototype skipped)
- Auth: <...>
- Error states: <...>
- Accessibility: <...>
- Security: <...>
- Performance: <...>
- Data model: <...>
## Data and privacy
- Real customer data used in prototype tools: <no | yes - approval reference>
- <Where the prototype data came from; what the tool retains>
## Security
- <Secrets used? Repo/tool access? Is generated code being merged? Review path>
## Accessibility
- <Baseline for the production build, e.g. WCAG 2.2 AA, plus known gaps from testing>
## IP and licensing
- <Tool terms reviewed? Output ownership? Third-party assets, fonts, code licenses>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |