菜单
Generate product content — one-pagers, pitch decks, README rewrites, comparison pages — from positioning research and codebase artifacts
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | product:brief |
| description | Generate product content — one-pagers, pitch decks, README rewrites, comparison pages — from positioning research and codebase artifacts |
| argument-hint | [format: readme|onepager|pitch|comparison|all] [--from positioning.md path] |
| user-invocable | true |
References: @product
Generate polished product content from your positioning document and codebase. Every claim is grounded in positioning decisions backed by research, and every technical claim is verifiable from the codebase.
$ARGUMENTS
| Input Pattern | Scope | Action |
|---|---|---|
readme | README rewrite | Generate a positioning-aligned README |
onepager | Product one-pager | Generate a one-page product summary |
pitch | Pitch content | Generate pitch deck narrative and key slides content |
comparison | Comparison page | Generate competitive comparison from research |
all or empty | All formats | Generate all content types |
--from <path> | Source | Use specified positioning doc (default: ./planning/positioning.md) |
/product:position first to create ./planning/positioning.md. Brief generates content from positioning decisions; without them, it has nothing to ground in./product:position first or proceed with a lightweight version using only codebase artifacts (with a warning that content will be weaker).Before generating content, validate that positioning research is current:
last_research date in the positioning document/product:position before generating contentFor each requested format, load the template and fill from positioning + verified codebase facts. Constraints for each format stay with the template file (honest comparisons, verified install commands, etc.).
| Format | Template | Notes |
|---|---|---|
| README | templates/readme.md | 30-second hero test; value-themed features |
| One-pager | templates/one-pager.md | Under ~400 words; live metrics |
| Pitch | templates/pitch-narrative.md | Slide narrative, research-sourced |
| Comparison | templates/comparison.md | Honest "choose them when"; cite competitor sources |
Apply @product messaging clarity hierarchy throughout.
Save generated content to ./planning/product-content/:
planning/product-content/
readme-draft.md
one-pager.md
pitch-narrative.md
comparison.md
Present each generated document with a summary of sources used and confidence level.
Brief consumes the positioning document. Position decides what to say; brief decides how to say it. Always run position first.
After generating content and applying it to the project, run audit to verify the new content is consistent across all surfaces.
README and comparison page content can be applied to the project as implementation tasks via execute.
Backlog-scale orchestration on top of /workflow — drives PM items through refine → plan → implement → review → local-merge via role-specialized sub-agents dispatched in parallel waves, each item isolated in its own git worktree. Bare /swarm summarizes state; /swarm <goal> runs the orchestrator; /swarm:setup sets up the charter and .agent-tools/ umbrella; /swarm:continue resumes a paused run.
Capture durable knowledge from any engineering work — debugging solutions, refactors, features, design decisions, reusable patterns — and maintain memory quality so each unit of work compounds the next
Principal workflow entry — resolve portfolio mode (swarm resume/handoff or unit state machine), drive work without inventing path; hard-stop when path is not established
Initialize and maintain planning root (.agent-tools/planning preferred), conventions (tracks, gates, integration), runs ledger scaffold, and shared memory under .agent-tools/memory/ (AGENTS.md memory-link) for the workflow family.
Parent skill for the workflow family — principal session entry is /workflow:continue (also bare /workflow). Horizon mapping, brainstorm, refine, plan, execute, review, audit, compound. Vertical-slice and deliverable-partition modes.
Detect gaps in the canonical skill corpus, propose targeted improvements, validate changes, and present for review. Inventories src/** skill trees; optional run-ledger seeds for process IP gaps.