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/hypotheses_sample.json
View on GitHub{
"initiative": "Expense approvals on mobile",
"as_of": "2026-09-21",
"constraints": {
"real_data_approved": false,
"max_days": 10
},
"hypotheses": [
{
"id": "H1",
"statement": "Approvers will clear pending expenses from a mobile push notification instead of waiting for the weekly desktop session",
"uncertainty": "desirability",
"impact": 5,
"evidence": "anecdotal",
"interactive_flow": true,
"target_segment": "Finance approvers at 50-500 employee customers",
"success_metric": "Approvers who opt in to the mobile pilot waitlist after the concept test",
"threshold": "at least 6 of 10"
},
{
"id": "H2",
"statement": "Approvers can review a receipt, spot a policy violation and approve or reject in under 60 seconds on a phone",
"uncertainty": "usability",
"impact": 4,
"evidence": "none",
"dynamic_states": true,
"target_segment": "Finance approvers at 50-500 employee customers",
"success_metric": "Unassisted task success on the 'reject an out-of-policy receipt' task",
"threshold": "at least 5 of 6 participants, median under 60 seconds"
},
{
"id": "H3",
"statement": "Receipt OCR plus policy rules can flag out-of-policy lines with acceptable accuracy",
"uncertainty": "feasibility",
"impact": 4,
"evidence": "qualitative",
"needs_real_data": true,
"target_segment": "Engineering spike (no users)",
"success_metric": "Precision of out-of-policy flags on a 200-receipt synthetic set",
"threshold": "at least 90 percent precision"
},
{
"id": "H4",
"statement": "Customers will pay for mobile approvals as part of the Business tier upgrade",
"uncertainty": "viability",
"impact": 3,
"evidence": "none",
"target_segment": "Economic buyers on the Standard tier",
"success_metric": "Upgrade intent in pricing conversations",
"threshold": "at least 3 of 8 buyers ask for a quote"
}
]
}
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 |