Generate Layer-6 System Requirements documents with traceability to upstream artifacts.
npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-sys
Please help me install this Agent Skill. Skill: doc-sys Source: https://github.com/vladm3105/aidoc-flow-framework/tree/main/.claude/skills/doc-sys Command: npx skills add https://github.com/vladm3105/aidoc-flow-framework --skill doc-sys
This Skill helps create System Requirements (SYS) documents that specify functional capabilities and quality attributes at the system level, ensuring consistent downstream decoupling into REQ and CTR artifacts.
Use doc-sys after ADR decisions to formalize system-level requirements and traceability.
High-intent search queries and answers about installing and using this skill.
System requirements documents formalize architecture decisions into Layer-6 SYS artifacts by capturing functional capabilities, quality attributes, and system flows with mandatory traceability back to ADR, BRD, PRD, EARS, and BDD artifacts. doc-sys enforces sequential numbering and template-based validation to ensure consistent downstream decoupling into REQ and CTR.
System requirements must document functional capabilities, quality attributes, system flows, and ADR-imposed technical constraints. doc-sys ensures these components are captured with Document Control metadata and traceable links to upstream decision records, creating a foundation for requirements and control layer derivation.
System requirements documents belong in Layer 6, after architecture decisions (Layer 5) are finalized. Use doc-sys to translate ADR decisions into comprehensive SYS artifacts that bridge high-level architecture and detailed requirements, establishing traceability and enforcing consistency before downstream decomposition.
doc-sys enforces consistency through mandatory Document Control, sequential requirement numbering, template-based validation, and standards checking. Traceability rules link each requirement to upstream artifacts (ADR, BRD, PRD, EARS, BDD), preventing orphaned or conflicting requirements.
System requirements are most effective after ADR decisions are documented; doc-sys is designed to translate those decisions into SYS artifacts. While you can create requirements independently, the Skill's core value is capturing ADR-imposed constraints and ensuring traceability, which requires upstream decisions.
System requirements capture quality attributes as part of Layer-6 SYS documentation. doc-sys provides template-based structure to document non-functional properties tied to architecture decisions, but the specific quality attributes depend on your ADR decisions and business priorities.
bkywksjDocument technology choices and rationale in Architecture Decision Records with enforced templates.
vladm3105Decompose BRD, PRD, and EARS inputs into atomic REQ v3.0 documents.
vladm3105Create formal EARS Layer 3 requirements documents using WHEN-THE-SHALL-WITHIN syntax.
vladm3105Create Architecture Decision Records with rationale, alternatives, and consequences.
