phuryn/product-engineering / product/skills/start-here
start-here
VerifiedWhere to start, and what comes next, along the product lifecycle: from a new idea, new evidence, an agreed change, a bug or a release to the next step and the skill that does it. Started by name only: /product:start-here in Claude Code, $product:start-here in Codex.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.8 KB |
| agents/openai.yaml | config | 43 B |
| receipts.md | markdown | 1.6 KB |
receipts.md
View on GitHub# start-here: receipts
Each heading is a rule from `SKILL.md`, with the case that taught it.
## Fetch first, because a checkout behind its remote describes the past.
- `2026-10-28`, a session read a product's docs from a checkout six days behind and reported its DNS provider as not set up, days after it had been.
## A test touching production, its users or its data runs only with your go.
- `2026-09-14`, a live Q&A product: asked for a per-IP rate limit, the plan's test section said the host's limits exist only on the host and couldn't be tested locally. The owner ran the plan with a test there, last: it sent requests from the tester's own address until the host refused one with HTTP 429, which blocks only that address for a minute, then checked that pages still loaded. Both limits were confirmed that way.
## Try visible phases after their checks; owner absence does not block coding.
- `2026-10-22`, a monitoring product: its review came back clean overnight; ten minutes of its owner using a preview that morning found six problems no review had, and each fix went back through review.
- `2026-11-16`, owner: phase previews follow the checks, while owner absence should not block the next phase. Early previews remain available when requested.
## The agent recommends stopping to use the product once it does its key job.
- `2026-11-19`: see `app-lifecycle`'s receipt of the same rule. The owner: "So maybe it's not about reviews, but also analyzing requirements and ordering requirements, which go to which phase and when you suggest me to stop and test it with the users early".
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |