<!-- Adapted from PM Agentic Cookbook source-intake, domain-modeling, create-prd and check-prd; modified by PM Agentic Cookbook contributors. SPDX-License-Identifier: Apache-2.0. See LICENSE and NOTICE. -->
PM AI Copilot — Requirements
Deliver professional, editable requirements with traceable business meaning. Support text in conversation and readable Markdown/plain-text files. Use host capabilities for other formats only when actually available and checked. Do not promise Word/PDF conversion or treat unreadable extracts as evidence. This skill produces requirements and checks; prototype generation and production implementation are separate tasks.
Choose the task and role first
- For an independent check, read review instructions and execute the reviewer role directly. Do not first load author notes or project memory. The caller supplies the target and approved comparison materials; missing context limits the check, not the source's legitimacy.
- For new requirements, an increment or a resumed authoring task, read project contract. Locate the user-selected project and actual current materials. Ask only if its directory, effective version or authority is unclear.
Resolve roles: this skill defines generic requirement work; a Provider is a set of business rules or conventions explicitly selected by the user; the Consumer supplies the current request, project locations and host capabilities. Do not infer or load an industry Provider from vocabulary alone. State which supplied business rules apply, or that none were supplied. Do not require a repository-wide setup, a separate acceptance checklist or another installed package.
Authoring path
- Read and clarify. Use intake and modeling. Identify sources, confirmed facts, assumptions, conflicts and questions. Ask the smallest set of questions that changes the goal, scope, objects, relationships, states or rules. Preserve an oral brief in the project state so it can be referenced later. Do not force a material tier questionnaire or multiple intake reports.
- Build the Domain Model. Read the Domain Modeling workflow and use its five-step method and model template. Preserve entity/field specifications, ER and relationship details, state, calculations, rules and applicable temporal/event constraints. Name new business documents <scope>_domain_model.md and <scope>_prd.md, matching their full titles; follow existing mappings or an authorized rename. Link them to sources. Present the model and scope for user confirmation; stop before generating a new PRD until they are confirmed. A previous explicit confirmation remains valid for its unchanged scope. Synchronize that actual confirmation into the current document and state; do not ask for it again as a ritual.
- Write or revise the PRD. Read the derived Create PRD workflow, its product-typing and applicable chapter references; use the 14-chapter PRD template. Preserve applicable detailed A–I page rules, permission structure, Overview/Sub ownership and the original self-check. Include core user scenarios, observable expected results and exceptions inside the PRD. Preserve existing authoritative document locations and identifiers. Load diagram rules when a diagram is needed. Do not require a separate acceptance-standard file or ledger.
- Check as author, then hand off. Save the complete author self-check separately from the business document. Read review instructions to prepare a clean handoff into a new WorkBuddy conversation. Give paths and exact reviewed versions, approved source/model, relevant rules, instructions and a unique report location. Freeze the business inputs and local resources; extract a section-mapped review copy for mixed documents. Omit author assessments, expected defects and previous conclusions from both the request and first-stage inputs. Rechecks deliver old reports only after the current judgment is written. Ask the user to open that independent conversation; do not continue in the author's context and call it independent. The installed resource path is resolved from this skill, never from a hard-coded machine path.
- Handle real findings. Read the actual independent report, present its findings and disagreements accurately, and obtain any required business decision or edit authority. Fix only the authorized scope, preserve previous content as required by the project contract, and request a separate check of changed items and adjacent effects. A reported issue, an author fix and a reviewer recheck are distinct results.
- Close the session. Read back real deliverables and update the project state, pending questions, meaningful history and next action. Record actual choices and reasons or say no new business decision was made. Return artifact locations, confirmation states, checks and remaining limits. Do not claim approval or acceptance on the user's behalf.
Stop affected work
Stop and describe the needed input when the project location or effective authority is ambiguous, a key business rule is unsupported, sources conflict, confirmation is missing, a required reference cannot be read, or a proposed edit exceeds authorization. Unaffected work may continue when its boundary is clear. Never fill a gap with a plausible enterprise default and label it confirmed.
For an independent check, decline the independent label if you authored the target or inherited author conclusions. A new conversation with only the review contract is the supported handoff. Do not promise invisible process or memory isolation. If that handoff cannot be performed, return the request and mark the independent check unperformed.
Source and license
This skill is derived from the author's open-source project PM Agentic Cookbook. Copyright 2026 Sunnyshinnny776 and contributors. Its PRD creation and checking workflows include adaptations of 杨堃 (pmYangKun)'s create-prd-skill and check-prd-skill, through Cookbook. Preserve their authorship, methodology attribution and applicable contributor notices. The upstream notices, including the applicable @Scofy0123 contribution, remain in NOTICE; the Apache-2.0 text is in LICENSE. The adaptations do not imply upstream endorsement.
