pftom
a98096a042
- Created .gitignore to exclude build artifacts and dependencies. - Added index.html as the main entry point for the application. - Included LICENSE file with Apache 2.0 terms. - Initialized package.json and package-lock.json for project dependencies. - Added pnpm-lock.yaml for package management. - Created QUICKSTART.md for setup instructions. - Added README.md and README.zh-CN.md for project documentation in English and Chinese.
1.5 KiB
1.5 KiB
name, description, triggers, ocd
| name | description | triggers | ocd | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| pm-spec | Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档". |
|
|
Product Spec Skill
Produce a one-page product spec / PRD.
Workflow
- Read the active DESIGN.md.
- Identify the feature + audience from the brief.
- Layout:
- Header strip: title, status pill (Draft / Review / Approved), date, owner.
- Three-line summary at the top — what, who, why now.
- "Problem" panel with one paragraph and a quote from a customer or internal partner.
- "Goals & non-goals" two-column block.
- "Success metrics" table with metric / target / measurement.
- "User stories" list with as-a / I-want / so-that format.
- "Scope" milestone tracker (3–4 phases).
- "Open questions" with assignee chips.
- One inline
<style>, semantic HTML, accent used twice max.
Output contract
<artifact identifier="spec-name" type="text/html" title="Spec Title">
<!doctype html>...</artifact>