requirement-discovery
MUST use before brainstorming, visual companion, Pencil/Figma, or implementation when a user gives a rough product, feature, app, website, landing p…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
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_workspacereview_artifact_contractreview_stage_gate
Hard Stops
- Do not let
brainstormingreplace 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-linemust produce a usable draft.over-clarificationmust block when the agent asks too many questions without a draft.empty-requirement-discoverymust block.
Next Gate
- Product scope may proceed only after
review_artifact_contractpasses for requirement discovery.
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
它属于哪个仓库
plugins/kevin592/codex-full-stack-workflow/skills/requirement-discovery/SKILL.md