woos-architecture-review-gate

النجوم٧

التفرعات١

آخر تحديث١٦ يونيو ٢٠٢٦ في ١٠:١٦

Independent high-level architecture review gate for discovery.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

المصدر

zero-click

zero-click/zero-ratchet

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

متخصصو إدارة المشاريعمهن الأعمال والعمليات المالية·SOC 13-1082

مستكشف الملفات

2 ملفات

SKILL.md

readonly

name	woos-architecture-review-gate
description	Independent high-level architecture review gate for discovery.
version	1.0.0
author	Hermes Profile
license	MIT
metadata	{"hermes":{"tags":["product","discovery","architecture","review","gate"],"related_skills":["woos-product-discovery","woos-architecture-overview"]}}

Architecture Review Gate

Output Language

Author all user-facing prose (narratives, findings, summaries) in the user's most recent input language (e.g. if the user is writing in Chinese, write the PRD body, review findings, and summaries in Chinese).
Keep these tokens verbatim in English regardless of the user's language, because they are contract identifiers consumed by other skills and gates:
- Verdict tokens: PASS, REQUEST_CHANGES, BLOCKED, NOT_RUN
- Severity tokens: critical, high, medium, low, warning
- Tag tokens: [ASSUMPTION: ...], [NEEDS CLARIFICATION: ...], [NEEDS INPUT: ...]
- Phase / dimension IDs: P0 … P11, P2a, Phase A, Phase B
- Shape values: internal-tool, single-operator, consumer-product, multi-stakeholder, CLI
- P0 rating values: strong, adequate, thin, broken
- Section headings declared in templates (e.g. ## Background, ## Functional Requirements, ## Assumptions Index) — translations break downstream structural checks
- Field labels inside templates (e.g. **Consequences (testable):**, **Out of Scope:**, **User value:**, Given … When … Then …)
Code, file paths, IDs, and quoted PRD excerpts stay in their original form.

Purpose

Review the architecture overview in fresh context before discovery completes.

Required Load Set (mandatory)

references/framework-architecture-validation.md
docs/product/<project>-architecture.md
docs/product/<project>-roadmap.md

If any required file is not loaded, return BLOCKED.

Output

docs/reviews/<project>-architecture-review-rN.md

Checklist

#	Criterion	Fix Hint
A1	Component boundaries	Split unclear or overloaded components
A2	Communication consistency	Pick one dominant pattern and justify exceptions
A3	Data decoupling	Add boundaries where raw sharing is too tight
A4	Infrastructure proportional	Avoid premature infra for later versions
A5	Dependencies manageable	Mark independent vs sequential buildability
A6	Risks realistic	Add concrete mitigations
A7	Version-aligned	Keep V2+ only elements out of V1 baseline

Every row must have a finding and status.

المزيد من هذا المستودع

نفس المستودع

woos-architecture-overview

zero-click/zero-ratchet

Produce the high-level architecture overview used by downstream product design and engineering.

2026-06-167

woos-idea-capture

zero-click/zero-ratchet

Capture and structure raw ideas through guided interview or quick note. Produces a structured idea document ready for research or PRD pass. Focuses purely on product intent — no technical decisions.

2026-06-167

woos-idea-to-design

zero-click/zero-ratchet

Entry-point product workflow from raw idea to validated product design artifacts. Stops at reviewed PRD readiness and does not include engineering implementation.

2026-06-167

woos-prd-authoring

zero-click/zero-ratchet

Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template.

2026-06-167

woos-prd-consistency-audit

zero-click/zero-ratchet

Dedicated analyze gate for PRD and UI brief consistency. Runs script extraction first, then semantic review with evidence-backed findings.

2026-06-167

woos-problem-validation

zero-click/zero-ratchet

Validate whether the captured problem is real, painful, frequent, and worth pursuing before broader discovery work begins.

2026-06-167

Architecture Review Gate

Output Language

Author all user-facing prose (narratives, findings, summaries) in the user's most recent input language (e.g. if the user is writing in Chinese, write the PRD body, review findings, and summaries in Chinese).

Keep these tokens verbatim in English regardless of the user's language, because they are contract identifiers consumed by other skills and gates:

Verdict tokens: PASS, REQUEST_CHANGES, BLOCKED, NOT_RUN
Severity tokens: critical, high, medium, low, warning
Tag tokens: [ASSUMPTION: ...], [NEEDS CLARIFICATION: ...], [NEEDS INPUT: ...]
Phase / dimension IDs: P0 … P11, P2a, Phase A, Phase B
Shape values: internal-tool, single-operator, consumer-product, multi-stakeholder, CLI
P0 rating values: strong, adequate, thin, broken
Section headings declared in templates (e.g. ## Background, ## Functional Requirements, ## Assumptions Index) — translations break downstream structural checks
Field labels inside templates (e.g. **Consequences (testable):**, **Out of Scope:**, **User value:**, Given … When … Then …)

Code, file paths, IDs, and quoted PRD excerpts stay in their original form.

Purpose

Review the architecture overview in fresh context before discovery completes.

Required Load Set (mandatory)

references/framework-architecture-validation.md

docs/product/<project>-architecture.md

docs/product/<project>-roadmap.md

If any required file is not loaded, return BLOCKED.

Output

docs/reviews/<project>-architecture-review-rN.md

Checklist

Criterion

Fix Hint

Component boundaries

Split unclear or overloaded components

Communication consistency

Pick one dominant pattern and justify exceptions

Data decoupling

Add boundaries where raw sharing is too tight

Infrastructure proportional

Avoid premature infra for later versions

Dependencies manageable

Mark independent vs sequential buildability

Risks realistic

Add concrete mitigations

Version-aligned

Keep V2+ only elements out of V1 baseline

Every row must have a finding and status.