Skip to main content

requirement-discovery

MUST use before brainstorming, visual companion, Pencil/Figma, or implementation when a user gives a rough product, feature, app, website, landing page, brand site, front-end design draft, or "do not develop yet" goal. Draft the first structured requirement contract and fixed workspace before design or implementation.

来源信息

仓库
hashgraph-online/awesome-codex-plugins
最近来源活动
2026年8月9日 14:43
检测到的 SKILL.md 语言
英语
星标
1,230
分支
343

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
requirement-discovery
description
MUST use before brainstorming, visual companion, Pencil/Figma, or implementation when a user gives a rough product, feature, app, website, landing page, brand site, front-end design draft, or "do not develop yet" goal. Draft the first structured requirement contract and fixed workspace before design or implementation.
# Requirement Discovery This skill turns a rough user goal into the first product-development contract. The user only needs to provide a rough goal, corrections, and confirmations. The agent must draft information architecture, draft interaction structure, draft state requirements, draft API/data assumptions, and draft acceptance boundaries. Do not ask the user to provide IA, interaction matrices, state matrices, API contracts, or acceptance criteria from scratch. ## Entry Rule For one-line site or design requests, start here. Examples: - "I want a high-end coffee brand website, make the front-end design draft first, do not develop." - "Create a SaaS landing page design." - "I need an admin dashboard concept." Do not offer a browser visual companion, open a local URL, start Pencil/Figma, or run a creative-only brainstorming flow before this skill has produced the fixed requirement workspace through `generate_requirement_workspace`. If brainstorming is useful, capture the idea as `AI Assumptions` inside the requirement discovery artifact, then ask at most three focused confirmation questions. ## Input Artifacts - User rough request - Existing project context when available - Prior change record when this is a resumed or changed feature ## Output Artifact - `docs/full-stack-development/requirements/<feature-slug>/01-intake/requirement-discovery.md` ## Required MCP Tool - `generate_requirement_workspace` - `review_artifact_contract` - `review_stage_gate` ## Hard Stops - Do not let `brainstorming` replace requirement discovery for product, website, landing page, brand site, or design-draft requests. - Do not offer browser visual companion or local URL preview before `generate_requirement_workspace`. - Do not enter Pencil/Figma. - Do not write implementation code. - Do not ask more than at most three focused questions before drafting assumptions. - Do not treat a chat summary as a project artifact. ## Pressure Test Responsibility - `rough-admin-one-line` must produce a usable draft. - `over-clarification` must block when the agent asks too many questions without a draft. - `empty-requirement-discovery` must block. ## Next Gate - Product scope may proceed only after `review_artifact_contract` passes for requirement discovery.
在 GitHub 查看