Product capability: turn PRD intent into an implementation-ready contract
Translate roadmap asks and product discussions into capability plans — constraints, invariants, interfaces, open questions
- What
- Translate roadmap asks and product discussions into capability plans — constraints, invariants, interfaces, open questions
- Cost
- Free
- Needs
- a PRD, roadmap item or product discussion to apply it to; nothing else — the skill is a planning methodology, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's product-to-engineering translation lane: turns PRD intent, roadmap asks or founder notes into an implementation-ready capability plan instead of vague planning prose. The workflow: restate the capability as one precise statement (who, what new capability exists after shipping, what outcome changes), extract the constraints that must hold before implementation (business rules, scope boundaries, invariants, trust boundaries, data ownership, lifecycle, rollout, failure/recovery), produce an SRS-style contract (actors, surfaces, states and transitions, interfaces, data-model implications, security/billing/policy constraints, observability, open questions), and hand off with an exact next step. Non-negotiable rules: never invent product truth, mark unresolved questions explicitly, and prefer one durable capability artifact (in `PRODUCT.md` or a capability manifest) over scattered ad-hoc notes. By @affaan-m, listed here with credit to its creator. Honest caveats: references companion ECC lanes (`project-flow-ops`, `tdd-workflow`, `verification-loop`, …) not included here; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a PRD, roadmap item or product discussion to apply it to; nothing else — the skill is a planning methodology, no accounts or keys required Install "Product capability: turn PRD intent into an implementation-ready contract" for me. Give my agent @affaan-m's product-capability lane: translate product intent into an implementation-ready capability plan — restate the capability in one precise statement, extract the constraints that must hold before implementation, produce an SRS-style contract (actors, surfaces, states and transitions, interfaces, data implications, security/billing/policy constraints, observability, open questions), and hand off with an exact next step. Never invent product truth; mark unresolved questions explicitly. Repository: https://github.com/affaan-m/ecc/blob/main/.agents/skills/product-capability/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "product-capability". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a methodology; point it at a real PRD or roadmap item). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.