loupe-stage-product-design
Use when a prompt names loupe-stage-product-design, or when a card's product document needs one review round.
- License 许可
- AGPL-3.0
- 所属仓库
- loupe-ac/loupe
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- loupe-stage-product-design
- description
- Use when a prompt names loupe-stage-product-design, or when a card's product document needs one review round.
02 资源文件 5
- 参考文档references/design-principles.md1.3 KB
- 参考文档references/product-document.md6.4 KB
- 参考文档references/review-round.md2.8 KB
- 脚本references/routing-check.sh1.8 KB
- 参考文档references/stage-contract.md14.1 KB
03 SKILL.md 正文
Product design stage
Revise the product document of one card, and stop. Leave architecture, entity and module decisions to the tech design stage.
Change nothing but Loupe documents, and never move the card. references/stage-contract.md holds the full rules.
Procedure
- Read
references/stage-contract.md. Follow its rules for the whole run. - Load the unattended run notes, as the contract says.
- Check the routing table, as the contract says. Load the skills that the
### Product designheading routes. - Connect to the Loupe tools, as the contract's first steps say.
- Call
card_get, and run the contract's column check. - Load
loupe-documents, then readreferences/product-document.mdandreferences/design-principles.md. Apply the principles to each change you make. - Find the product document among the linked documents, as the contract says. It has the product design tag, or a title that starts
Product design. - When step 7 finds none, search
document_listfor the titleProduct design: <card title>, as the contract says.
Revise, when step 7 or 8 finds the document
- When its
statusisapproved, stop withSTAGE RESULT: product document already approved. - Read code and docs only to state current behaviour.
- Follow
references/review-round.md. The document isproduct document, and the requirement source is the card body.
Stop, when neither step finds a document
- Stop with
STAGE RESULT: no product document; run /loupe-lifecycle:product-design. The owner writes the document in that session.
Write the final reply, its reason code and the structured result as the contract "Final reply" section says.
04 同仓库更多 Skills
loupe-workers
Use when reading worker runs or bridges through the loupe MCP, stopping, resuming or holding workers, cancelling a bridge command, or recovering workers after a usage limit or network outage.
loupe-site-review
Use when acting on live-review feedback through the loupe MCP: reading the feedback of a card or project, fixing it, or marking it addressed.
loupe-inbox
Use when an agent needs a decision, answer or review from the project owner through the loupe MCP, hands a question or to-do to a person, resumes after an ask closed, or needs its session id.
loupe-documents
Use when writing or revising a document for the Loupe app through the loupe MCP, such as a plan, spec, RFC, audit report or retrospective.
loupe-discovery
Use when a bridge runs a discovery run of a Loupe project, when a prompt names loupe-discovery, or when writing a readiness report.
loupe-board
Use when working a Loupe project board through the loupe MCP: reading or writing a card, moving a card, changing the columns, or linking a document or a pull request to a card.