← ClaudeAtlas

senmu-build-productlisted

Define durable product scope, version placement, priority, acceptance, state, and cross-page interface content. Not for one-off edits, implementation review, technical design, or deployment.
SenMuShare/senmu-buildos · ★ 2 · Web & Frontend · score 73
Install: claude install-skill SenMuShare/senmu-buildos
# Product Management Maintain one truth chain across optional requirements, version PRDs, current product specifications, and acceptance. Continue only for durable contract, version-placement, or cross-page content changes. ## Route by Outcome - Requirements, versions, document transitions, freezing, reconciliation: [Product Iteration](references/product-requirements-and-iteration.md). - Cross-page labels, user-facing state copy, error messages, terminology, generated content: [Interface Content](references/interface-copy-and-content-design.md), then only [Chinese](references/chinese-interface-copy.md) or [English](references/english-interface-copy.md). Fill gaps in existing standards. Read a [User Requirements](assets/product-governance/USER_REQUIREMENTS.template.md), [Version PRD](assets/product-governance/PRD.template.md), or [Product Specification](assets/product-governance/PRODUCT_SPECIFICATION.template.md) template only when creating it. Decide low-risk discussions directly. ## Core Contract - The user decides goals, preferences, and authorization; questions, claims, and proposals are inputs. Distinguish facts, expectations, assumptions, and advice. Judge independently from evidence, counterexamples, alternatives, cost, and risk. Explain material disagreement; after an informed decision, act within authorization and Kernel boundaries. - Assign work to the current version, a successor, or an optional backlog. Infer when facts suffice; ask only if placement changes