product-builder-resolver
Skill5 starsChanged 26 days agoMITView on GitHub
The capability index of the product-builder pack — which skill answers which capability, and where each one lives once installed. Load it to route a request to the right skill of the pack instead of guessing, and to see what the pack does not cover.
In this repository12 other files it gives its agents.
- cpoSkill
- ctoSkill
- grillSkill
- ideation-engineSkill
- insight-engineSkill
- market-researchSkill
- prdSkill
- product-metricsSkill
- product-strategySkill
- synthetic-usersSkill
- ux-researchSkill
- visual-designerSkill
The file
Files
product-builder — the pack resolver
One row per capability. The Tool column names the skill to load; the Path column is where that skill
lives once npx skills add pedroromeroluna/ai-first-product-skills has installed it.
| Capability | Tool | Path |
| Define the problem, the evidence behind it and the prioritized hypotheses of a product | product-strategy | .agents/skills/product-strategy/SKILL.md |
| Research the market with secondary research and size the opportunity | market-research | .agents/skills/market-research/SKILL.md |
| Plan the qualitative or quantitative research round on the riskiest hypothesis | ux-research | .agents/skills/ux-research/SKILL.md |
| Pilot a research script with synthetic personas before real fieldwork | synthetic-users | .agents/skills/synthetic-users/SKILL.md |
| Converge the evidence of real fieldwork into insights, the customer profile and prioritized opportunities | insight-engine | .agents/skills/insight-engine/SKILL.md |
| Prepare the ideation workshop and converge its results into the value map and the prototype brief | ideation-engine | .agents/skills/ideation-engine/SKILL.md |
| Specify a visual piece —interface, deck, infographic— and build it when a design tool is connected | visual-designer | .agents/skills/visual-designer/SKILL.md |
| Define the North Star, the metric tree and the metric of each active hypothesis | product-metrics | .agents/skills/product-metrics/SKILL.md |
| Interview and write the strategic layer of a product | prd | .agents/skills/prd/SKILL.md |
| Act as standing CPO over the product of an organization | cpo | .agents/skills/cpo/SKILL.md |
| Act as standing CTO over the technical architecture of an organization's product, software and AI systems included | cto | .agents/skills/cto/SKILL.md |
A request that no row covers is not answered by improvising one of these skills: the missing capability is named instead. This index is the pack's own — it never routes anything outside it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

