一键在 Manus 中运行任何 Skill

wisedev-requirement-spec

星标0

分支0

更新时间2026年4月19日 06:52

write structured chinese requirement specifications from rough needs, clarified requirement briefs, transcripts, or mixed materials. use when the user needs a formal markdown requirement document with scope, actors, scenarios, functional requirements, non-functional requirements, acceptance criteria, and traceable identifiers in a government or enterprise documentation style.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

hu-qi

hu-qi/wisedev-suite

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

目标

在 using-wisedev 已确认这是明确单阶段任务，或 wisedev-orchestrator 已完成阶段判断后，再由本 Skill 处理当前阶段。

首次执行本阶段任务时，优先参考 references/example-library.md；若输入与“上传下达模块”高度相似，再对照 ../shared/full-chain-examples/case-01-upload-delivery/02-requirement-spec.md 的本阶段样例。

输出正式、可评审、可追踪的《需求规格说明书》。

输入前提

优先使用以下任一输入：

已整理的需求简报
会议纪要转需求梳理结果
用户直接给出的结构化业务需求

文风要求

偏政企 / 国企正式文档风格。
避免互联网产品口语化表达。
使用“应支持 / 应具备 / 应满足 / 系统应能够”等表述。

必须包含的章节

文档概述
项目背景与建设目标
角色与参与方
业务场景
范围界定
功能需求
非功能需求
业务规则
验收标准
风险与待定事项
术语表

写作规则

所有关键需求必须分配稳定编号，如 FR-001、NFR-001。
每一项功能需求应可被测试验证。
对优先级不明确的要求，默认不做强行排序，但可用“核心 / 重要 / 可选”分组。
需要时补充“范围外事项”，避免范围蔓延。

高质量样例优先

优先参考 references/example-library.md 和 references/examples/ 下的案例，沿用其中的编号方式、正式文风和验收标准粒度。

可用资源

references/requirement-principles.md
references/scope-rules.md
templates/srs-template.md
templates/acceptance-criteria.md
templates/glossary.md
templates/functional-requirement.md
templates/nonfunctional-requirement.md
templates/risk-and-issues.md
templates/business-scenario.md
templates/project-overview.md

同仓库更多 Skills

同仓库

using-wisedev

hu-qi/wisedev-suite

enforce wisedev workflow discipline before product-delivery tasks. use when the user asks for requirement clarification, requirement specifications, design documents, openapi yaml contracts, vue plus mock prototypes, or any request that may cross stages. require the assistant to check the wisedev skill suite first, route multi-stage tasks through wisedev-orchestrator first, and map clear single-stage requests to the correct wisedev child skill.

2026-04-220

wisedev-orchestrator

hu-qi/wisedev-suite

orchestrate staged delivery artifact generation from short requirements, meeting notes, transcripts, and mixed materials. use when the user wants to turn ambiguous chinese product or business input into structured outputs such as requirement briefs, requirement specifications, design documents, openapi yaml contracts, or vue plus mock prototypes. act as the mandatory entry skill for multi-stage work: identify the current stage first, normalize context first, choose one child skill first, and require stage handoff artifacts before any downstream stage.

2026-04-220

wisedev-vue-mock-prototype

hu-qi/wisedev-suite

generate vue-based frontend prototype plans and code scaffolds with local mock services from chinese requirement, design, and openapi artifacts. use when the user needs a modern vue 3 plus vite plus typescript plus pinia plus router prototype, with realistic mock data, workflow states, and local run instructions for complex enterprise business demonstrations.

2026-04-220

wisedev-prototype-design

hu-qi/wisedev-suite

recommend contrasting prototype design directions, generate theme token packages, and critique visual outputs for chinese enterprise-facing prototypes. use when the user needs design direction, visual style comparison, color schemes, prototype themes, or design review before or after vue prototype generation.

2026-04-210

wisedev-design-doc

hu-qi/wisedev-suite

generate chinese high-level and detailed design documents from requirement specifications, requirement briefs, or structured business input. use when the user needs architecture decomposition, module boundaries, role permissions, workflows, state transitions, data entities, interfaces, and exception handling documented in markdown in a formal enterprise style.

2026-04-190

wisedev-meeting-to-spec

hu-qi/wisedev-suite

analyze meeting notes, transcript text, and mixed chinese discussion materials and convert them into structured requirement inputs. use when the user provides a transcript, a meeting summary, or scattered discussion text and wants requirement clarification, feature extraction, role and scenario analysis, unresolved question tracking, or a draft requirement brief.

2026-04-190

name	wisedev-requirement-spec
description	write structured chinese requirement specifications from rough needs, clarified requirement briefs, transcripts, or mixed materials. use when the user needs a formal markdown requirement document with scope, actors, scenarios, functional requirements, non-functional requirements, acceptance criteria, and traceable identifiers in a government or enterprise documentation style.

目标

在 using-wisedev 已确认这是明确单阶段任务，或 wisedev-orchestrator 已完成阶段判断后，再由本 Skill 处理当前阶段。

输出正式、可评审、可追踪的《需求规格说明书》。

输入前提

优先使用以下任一输入：

已整理的需求简报
会议纪要转需求梳理结果
用户直接给出的结构化业务需求

文风要求

偏政企 / 国企正式文档风格。
避免互联网产品口语化表达。
使用“应支持 / 应具备 / 应满足 / 系统应能够”等表述。

必须包含的章节

文档概述
项目背景与建设目标
角色与参与方
业务场景
范围界定
功能需求
非功能需求
业务规则
验收标准
风险与待定事项
术语表

写作规则

所有关键需求必须分配稳定编号，如 FR-001、NFR-001。
每一项功能需求应可被测试验证。
对优先级不明确的要求，默认不做强行排序，但可用“核心 / 重要 / 可选”分组。
需要时补充“范围外事项”，避免范围蔓延。

高质量样例优先

优先参考 references/example-library.md 和 references/examples/ 下的案例，沿用其中的编号方式、正式文风和验收标准粒度。

可用资源

references/requirement-principles.md
references/scope-rules.md
templates/srs-template.md
templates/acceptance-criteria.md
templates/glossary.md
templates/functional-requirement.md
templates/nonfunctional-requirement.md
templates/risk-and-issues.md
templates/business-scenario.md
templates/project-overview.md