product-delivery
Skill1 starsChanged 51 days agoMITView on GitHub
For substantial website, app, and product work, guide the project from requirements through product brief, prototype, technical design, implementation, verification, and delivery.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- prayceo/claude-skills-publictheir own version, first seen Mar 20, 2026
- yannickYamo/skillstheir own version, first seen Feb 6, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- yannickYamo/skills★ 23same name
- prayceo/claude-skills-public★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- llms.txtllms.txt
- agentflow-osSkill
- api-and-interface-designSkill
- checkpoint-recoverySkill
- ci-cd-and-automationSkill
- context-engineeringSkill
- debugging-and-error-recoverySkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- interview-meSkill
- makecrewSkill
- parallel-dispatchSkill
- planning-and-task-breakdownSkill
- review-and-critiqueSkill
- self-evolutionSkill
- shipping-and-launchSkill
- skill-auditSkill
- source-driven-developmentSkill
- task-intakeSkill
- test-driven-developmentSkill
- verification-before-completionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this Skill for new or substantially redesigned websites, apps, products, and multi-stage features.
- Distinctive: line 14
Read the project rules, existing context, repository status, and startup/test commands.
- Very specific: line 21
Run tests and verify the key user flow in the target environment.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Delivery
Use this Skill for new or substantially redesigned websites, apps, products,
and multi-stage features. Keep small bug fixes, routine edits, and simple
queries on the shorter task-intake path.
Workflow
- Read the project rules, existing context, repository status, and startup/test commands.
- Clarify material gaps until the target, users, scope, constraints, and acceptance criteria are decision-ready.
- Produce a compact
project-brief.mdwith the goal, users, scope, non-goals, and measurable acceptance criteria. - Produce a
product-demo.mddescribing the core flow, states, and a minimal prototype or preview when useful. - Produce a
technical-design.mdcovering architecture, interfaces, data, dependencies, risks, and reversible choices. - List the matched Skills, tools, employees, deliverables, budget, and verification gates. Wait for confirmation before implementation when the plan changes scope or cost.
- Implement incrementally, keeping changes scoped to the approved plan and recording checkpoints.
- Run tests and verify the key user flow in the target environment. Record fresh evidence in
verification-report.md. - Present the delivered artifact, evidence, known limits, rollback point, and next action.
Context and cost
Reuse the project context and employee thread where compatible. Pass task deltas, not complete histories. Do not run this full workflow for routine maintenance.
Output contract
Return the approved scope, selected Skills/tools, artifacts, checkpoints, verification evidence, risks, and delivery status. A plan or queued host task is not a completed delivery.
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.