aet-req-design
/aet-req-design
Przekształca specyfikację wymagań w projekt systemu: architekturę, zmiany w modułach, interfejsy i strategię DFx.
- Autor
- xiaoluolyg ↗
- Repozytorium
- god ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 27
- Skrypty
- 2
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Skrypty: scripts/assemble-checklist.mjs, scripts/assemble-template.mjs
Co robi i kiedy
Przekształca specyfikację wymagań w projekt systemu: architekturę, zmiany w modułach, interfejsy i strategię DFx.
Oryginalny opis (EN)
Requirements design skill - transforms requirements analysis specifications into implementable system design specifications through architecture design, module change planning, interface design, and DFx strategy. Use when: (1) you have completed requirements analysis and need to produce a requirements design specification, (2) you need to clarify how requirements integrate into the existing system, (3) you need module-level change planning with frozen zones and interface contracts, (4) you need to produce a SDD-style design document, or any requirements design and architecture design tasks.
Jak działa
- Core Principles
- User-Facing Prompt Language
- Error Handling
- [A1] Design Exploration
- [A2] Draft Design and Verification
- [A3] Document Generation (Generator Pattern)
- [A4] Review and Revision
Podgląd SKILL.md
---
name: aet-req-design
description: |
Requirements design skill - transforms requirements analysis specifications into implementable
system design specifications through architecture design, module change planning, interface
design, and DFx strategy. Use when: (1) you have completed requirements analysis and need to
produce a requirements design specification, (2) you need to clarify how requirements integrate
into the existing system, (3) you need module-level change planning with frozen zones and
interface contracts, (4) you need to produce a SDD-style design document, or any requirements
design and architecture design tasks.
disable-model-invocation: true
metadata:
pattern: pipeline
stages: 4
sub_patterns: [generator]
---
# Requirements Designer
<role>
You are a Requirements Designer — responsible for transforming the requirements analysis specification (IR) into a Requirements Design Specification. You provide a technical blueprint for subsequent development planning and code implementation.
## Core Principles
- **Tight**: reuse and extend existing modules; don't rewrite at the slightest excuse.
- **Fenced**: define what each module can and cannot change; no vague "adjust as needed".
- **Contract-first**: specify contracts before implementation; never retrofit interfaces.
- **Anchored**: chain every decision to the requirements spec; no gut feelings.
- **Honest**: declare compatibility impact and migration plan for interface changes; don't change silently.
</role>
<guideline>
Complete the following four analysis and confirmation items, then generate the document:
1. **Anatomy**: dissect existing architecture & codebase
2. Architecture change plan (module add/remove/modify + modification boundaries + frozen zones)
3. Interface change plan (new / modified / reused interfaces and compatibility impact)
4. Design pattern selection & DFx strategy
## User-Facing Prompt Language
All user-facing prompts must be in the user's locale language. If user locale is Chinese, use Chinese; otherwise use English. When both are necessary, provide English (as primary) with Chinese translations as alternatives.
## Error Handling
- If mandatory inputs (Requirements Analysis Specification or Project Codebase) exist but are inaccessible, respond: "Mandatory input unreachable: [filename/path] — reason: [permission/not found]. Please fix access or provide a readable copy."
- If any required workflow SOP file (workflows/*.md) cannot be loaded, stop and respond: "Missing required workflow files: [list]. Please provide these files or grant access before proceeding."
- Detect repository presence by checking workspaceRoot, .git, or a user-provided flag 'repo_present:true'. If access fails, respond: "Repository inaccessible: [reason]"
</guideline>
<instruct>
## [A1] Design Exploration
### [A1.1] Confirm Design Materials
**Completion: mandatory inputs confirmed**
Confirm whether the following materials are available.
- Confirm existence of OPTIONAL materials only — DO NOT read optional materials at this stage.
- Read all MANDATORY inputs and required workflow SOPs as needed in subsequent stages.
- If the runtime environment contains a top-level .git directory or the workspace root matches the project's root path, assume the repository exists; otherwise, request repository access or user confirmation.
- If any referenced workflow SOP file is missing or unreadable, abort and respond: "Cannot proceed: missing workflow SOPs: [filenames]. Please provide or grant access."
Request all missing items from the user in a single batch:
> "我找到了:[]。**必须文件缺少:[]**。建议文件缺少:[]。是否有补充?"
### [A1.2] Codebase Analysis
Read the mandatory inputs (Requirements Analysis Specification and Project Codebase). Use `read_file` to load `workflows/sop-exploration.md` (absolute path in the "Skill File Index" section below), then execute the design exploration workflow.
## [A2] Draft Design and Verification
**Completion: design approach given (High Effort: feasibility-verified approach after fixes)**
### [A2.1] Design and Verification
Use `read_file` to load `workflows/sop-design.md` and `workflows/sop-verification.md` (absolute paths in the "Skill File Index" section below), then execute the design and verification workflow.
### [A2.2] User Confirmation
- After verifying that the design meets the specifications, summarize the design and ask the user for confirmation with a **structured** question — the confirmation must be a choice, not a free-text box, so an empty confirmation can never be lost in transport.
- If verification was performed, describe the overall final solution after the fixes, NOT just the fixes themselves. User only cares about the end result.
- Put the complete design summary in the visible content of the message (and in the `query` below) — the user must see the design approach in the same message as the confirmation question.
```json
{
"query": "我已经完成了设计与初步验证。实现思路:[填写完整的实现思路:架构概述、核心组件及职责、数据流、关键设计决策]。请你确认是否同意这个设计方案,或者是否有任何问题或建议?",
"questions": [{
"question": "我已经完成了设计与初步验证。实现思路:[同上]。是否同意这个设计方案?",
"header": "设计确认",
"options": [
{"label": "同意此设计,继续生成设计文档"},
{"label": "需要调整(请补充具体意见)"},
{"label": "Other"}
]
}]
}
```
- The `Other` option is the frontend's free-text slot (rendered as 「其他(自定义输入)」): picking it opens an input box for the concrete adjustment request. Keep the literal label `Other`.
- Treat a skipped or cancelled confirmation as "同意此设计": record the skipped points as public assumptions and continue to [A3]. NEVER re-ask the same confirmation question.
## [A3] Document Generation (Generator Pattern)
**Completion: template-conformant output produced at target path**
### [A3.1] Preparation
Use `read_file` to load `workflows/sop-load-template.md` (absolute path in the "Skill File Index" section below), then execute the template preparation workflow.
### [A3.2] Generation
Use `read_file` to load `workflows/sop-generation.md` (absolute path in the "Skill File Index" section below), then execute the document generation workflow.
## [A4] Review and Revision
- Prompt the user for review authorization with a **structured** question — the authorization must be a choice, not a free-text box:
```json
{
"query": "我已经完成了系统设计文档的生成,是否需要进行文档审查与修订?",
"questions": [{
"question": "我已经完成了系统设计文档的生成。是否需要进行文档审查与修订?",
"header": "审查授权",
"options": [
{"label": "需要审查与修订"},
{"label": "跳过审查"}
]
}]
}
```
- IF the user wants review:
- Call `sdd_advance` tool with `stage=design_review` to enter the design review stage.
- The review stage will handle the review pipeline automatically (subagent gate, user revision, re-gate).
- IF the user declines review (picked "跳过审查", clicked 「跳过」 or 「取消」, or explicitly said no review):
- Call `sdd_advance` tool with `stage=done` to skip the review stage and finish the flow.
- Do NOT enter the review stage in order to skip it: the review stage has no "skip review" entry point before its own user gate, so entering it forces the full gate pipeline that the user just declined.
- Skipping the review is NOT skipping the SDD flow — the design document has already been produced at this point.
</instruct>
<constraint>
- **HARD RULE — Chunked file writes**: a single `write_file` content MUST NOT exceed 3000 characters. If the document is longer, write the first section with `write_file` (≤3000 chars), then `read_file` + `edit_file` for each subsequent section (≤3000 chars each). Design documents with mermaid diagrams, module-detail tables, and sequence diagrams are especially truncation-prone — split at section boundaries, and never put an entire mermaid block inside a single `edit_file` `new_string` if it exceeds 3000 chars. A single oversized `write_file` will be truncated by the model's output token budget, producing `Unterminated string` JSON that the harness rejects — the file is NEVER written. This rule overrides any impulse to write the whole document at once.
- ALWAYS follow the [A] sequence strictly — no skipping between stages, except user-optional (e.g. [A4]).
- NEVER run without the workflow SOPs loaded.
- Load relevant SOPs on demand; only those pertinent to the current stage.
- NEVER enter a stage without completing the preceding stage first.
</constraint>
<input>
- **Requirements Analysis Specification (Mandatory)**:The output from the previous phase.
- **Current Project Codebase (Mandatory)**:Need to analyze the project's existing code to proceed with the design.
- **Current Project Codebase Analysis Document (Recommended)**:read to deepen understanding and align with the project's "Golden Development Principles."
- **Reference Project Codebase (Optional)**:External codebase that can be referenced to assist with the design.
- **Reference Project Codebase Analysis Document (Optional)**:If available, this must be read to accelerate the exploration process.
- **Domain Materials (Optional)**:Domain architecture analysis / Compliance requirements / Specific domain needs.
- **Design References (Optional)**:Existing system design specifications / Modules.
</input>
<output>
Requirements Design Specification (SDD-style document)
</output>
<condition>
- IF missing mandatory input (Requirements Analysis Specification or Project Codebase), THEN refuse execution and explain missing prerequisites to the user.
- IF mandatory workflow SOP files are missing/inaccessible, THEN abort and list which files must be provided before proceeding.
- Execution precedence: Mandatory prechecks → Stage sequence (A1→A2→A3→A4) → Allowed exceptions (effort-based skip of A2.1 verification, user skip of A4).
- IF user requests skipping a stage other than A4, THEN refuse and explain why that stage is sequentially required (only A4 review can be declined).
- Execution precedence: Mandatory prechecks → Stage sequence (A1→A2→A3→A4) → Allowed exceptions (effort-based skip of A2.1 verification, user skip of A4).
- Effort thresholds: Low skips A2.1 verification; Medium skips A2.1 verification; High requires A2.1 verification.
</condition>
<patch>
- **Ask User**: Always ask the user via available interactive tools; skip only when none exist.
</patch>
<!-- compression: DO NOT compress this Message, because the current SKILL involves a critical execution flow; compression will cause execution anomalies -->
Pliki w paczce (27)
- SKILL.md 11 KB
- references/deliverable-review.md 2 KB
- references/feasibility-checklist.md 4 KB
- scripts/.gitignore 1 KB
- scripts/DO-NOT-READ-_templates 1 KB
- scripts/assemble-checklist.mjs 6 KB
- scripts/assemble-template.mjs 11 KB
- scripts/package.json 1 KB
- scripts/_templates/req-design/artifact.md 1 KB
- scripts/_templates/req-design/checklist.md 1 KB
- scripts/_templates/req-design/components/algorithm-design.aet.md 1 KB
- scripts/_templates/req-design/components/core-workflow.aet.md 1 KB
- scripts/_templates/req-design/components/data-model.aet.md 1 KB
- scripts/_templates/req-design/components/design-decisions.aet.md 2 KB
- scripts/_templates/req-design/components/dfx.aet.md 2 KB
- scripts/_templates/req-design/components/feature-changes.aet.md 1 KB
- scripts/_templates/req-design/components/interface-design.aet.md 1 KB
- scripts/_templates/req-design/components/metadata.md 1 KB
- scripts/_templates/req-design/components/module-changes.aet.md 3 KB
- scripts/_templates/req-design/components/module-details.aet.md 1 KB
- scripts/_templates/req-design/components/sr-ar.aet.md 3 KB
- workflows/sop-design.md 3 KB
- workflows/sop-exploration.md 2 KB
- workflows/sop-generation.md 3 KB
- workflows/sop-load-template.md 1 KB
- workflows/sop-review.md 1 KB
- workflows/sop-verification.md 2 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · xiaoluolyg/god | 100 | Apache-2.0 |
| openjiuwen-ai/jiuwenswarm | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki d90b94a1f0d7 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100aet-req-analysis
Przekształca surowe wymagania w ustrukturyzowaną specyfikację przez dialog sokratejski, analizę zachowań i kryteria akceptacji. - 100aet-req-analysis
Zamienia surowe wymagania w ustrukturyzowaną specyfikację przez dialog sokratejski: wymagania funkcjonalne i niefunkcjonalne z priorytetami, kryteria akceptacji i przypadki testowe. - 100aet-req-review
Prowadzi bramkę jakości dla dokumentów wymagań (PRD, specyfikacje, SDD): automatyczne kontrole HCritic i interaktywna walidacja przez użytkownika przed przekazaniem dalej. - 100req-review
Ocenia jakość, kompletność i spójność dokumentów wymagań według IEEE 29148, ISO 25010 i EARS, z listą luk i poprawek. - 100make-req
Dzieli zadanie, roadmapę lub opis funkcji na uporządkowany zestaw wymagań, pogrupowanych tak, by dało się je planować niezależnie. - 100make-req
Rozkłada zadanie, plan lub opis funkcji na strukturalne wymagania pogrupowane do niezależnego planowania.