ワンクリックでManusで任意のスキルを実行

03-prd

スター29

フォーク2

更新日2026年6月11日 06:19

Generate a structured Product Requirements Document from a feature description or user stories, validated with the user before save. Use when the user says "prd", "draft prd", "write prd", "product requirements for X", "generate a prd", or invokes `/prd`. Do NOT use for writing user stories, drafting a technical implementation plan, or writing source code.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ai-driven-dev

ai-driven-dev/aidd-framework

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

PRD

Drafts a structured Product Requirements Document covering scope, goals, and acceptance criteria.

Available actions

#	Action	Role	Input
01	`prd`	Parse input, draft per template, validate, save	feature_description, user_stories (optional)

Default flow

Single action skill. The router dispatches to prd whenever a PRD-generation phrase appears.

Transversal rules

Focus on what and why; never include technical implementation detail.
Sections stay concise and actionable.
Always wait for explicit user validation before saving.
Save path: aidd_docs/tasks/<yyyy_mm>/<yyyy_mm_dd>-<feature_name>-prd.md.
Source of truth for structure: @assets/prd-template.md.

References

None.

Assets

@assets/prd-template.md: PRD body template.
@assets/task-template.md: Lightweight task template referenced from the PRD when needed.

External data

None.

このリポジトリの他の Skills

同じリポジトリ

00-onboard

ai-driven-dev/aidd-framework

Detect the current project's state and open a hub of project actions - understand the project, set up or refresh the memory bank, or continue the AIDD development journey. Silently inspects the project, the AIDD setup, and which AIDD plugins are installed, then adapts the menu to that context. Use when the user says "where do I start", "onboard me", "onboard me to this project", "what should I run next", "what should I work on next", "what's the state of this project", "guide me through aidd", "guide me through aidd-context", or invokes `aidd-context:00-onboard`. Do NOT use to enumerate every installed surface from raw user intent (the discovery skill in this plugin handles that).

2026-06-1129

01-bootstrap

ai-driven-dev/aidd-framework

Imagine and validate the technical architecture of a new SaaS through interactive Q&A, candidate-stack comparison, multi-agent audit, and an INSTALL.md output. Use when starting a new SaaS project, choosing a stack, designing the architecture pattern (monolith vs microservices vs serverless), or producing a project's INSTALL.md. Do NOT use for editing an existing project's stack, database schema design, or scaffolding actual files (this skill produces docs only, no code).

2026-06-1129

02-project-init

ai-driven-dev/aidd-framework

Initialize or refresh the project memory bank and ensure AI context files contain the project memory block. Use when running `aidd init` for the first time, bootstrapping a new project, or re-running the init flow on an existing project. Do NOT use for updating individual memory files after they exist - use `aidd-context:05-learn` instead; do NOT use for editing a single rule - edit the file directly.

2026-06-1129

03-context-generate

ai-driven-dev/aidd-framework

Generate context artifacts (skills, agents, rules, commands, hooks, plugins, marketplaces) across the host AI tool(s) the project uses. Use when the user wants to create, refactor, add or remove actions in a skill, migrate a legacy slash command into a router-based skill, or generate a new agent, rule, command, hook, plugin, or marketplace. Do NOT use for editing a single action inside an existing skill (edit directly), writing MCP servers, or modifying project-level files.

2026-06-1129

04-mermaid

ai-driven-dev/aidd-framework

Generate high-quality Mermaid diagrams from markdown content using a structured plan-validate workflow.

2026-06-1129

05-learn

ai-driven-dev/aidd-framework

Capture and store project-level learnings, conventions, and decisions surfaced during work into memory, decisions, or rules. Use proactively when the user states a durable project rule or convention ("for next", "always do X", "from now on", "going forward", "rule:", "convention:"), records a technical decision and its rationale, deprecates something, or notes an insight that should outlive the current task. Do NOT use for personal or AI-preference reminders (those belong to user memory), routine code edits, minor fixes, or anything already captured.

2026-06-1129

name	03-prd
description	Generate a structured Product Requirements Document from a feature description or user stories, validated with the user before save. Use when the user says "prd", "draft prd", "write prd", "product requirements for X", "generate a prd", or invokes `/prd`. Do NOT use for writing user stories, drafting a technical implementation plan, or writing source code.

PRD

Drafts a structured Product Requirements Document covering scope, goals, and acceptance criteria.

Available actions

#	Action	Role	Input
01	`prd`	Parse input, draft per template, validate, save	feature_description, user_stories (optional)

Default flow

Single action skill. The router dispatches to prd whenever a PRD-generation phrase appears.

Transversal rules

Focus on what and why; never include technical implementation detail.
Sections stay concise and actionable.
Always wait for explicit user validation before saving.
Save path: aidd_docs/tasks/<yyyy_mm>/<yyyy_mm_dd>-<feature_name>-prd.md.
Source of truth for structure: @assets/prd-template.md.

References

None.

Assets

@assets/prd-template.md: PRD body template.
@assets/task-template.md: Lightweight task template referenced from the PRD when needed.

External data

None.