Results for “sdr”

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Turns a brainstorm document into a comprehensive, structured software requirements specification with no word limit.

Guides a structured requirements pipeline from topic intake through brainstorming, spec and plan writing, user review, SRS generation, validation, and improvement reporting.

Generate structured Architectural Decision Record (ADR) documents with standardized front matter, consequences, and alternatives for AI-optimized decision documentation.

Reads a project spec and writes one detailed plan file per SRS section, producing a complete blueprint for SRS generation.

Generates a complete IEEE 830-compliant Software Requirements Specification from approved plan files, producing one file per section with no word limit.

Generates 12 detailed plan files from a project spec, one per SRS section, with FR/NFR numbering and a summary table.

Classifies medical devices under EU MDR 2017/745 Annex VIII rules, including software per MDCG 2019-11, with examples and conformity assessment routes.

Turns a brainstorm document into a structured software requirements specification with actors, features, business rules, and non-functional requirements.

Write and maintain Architecture Decision Records (ADRs) — when to write one, the standard format, status lifecycle, how to link related decisions, and how to surface ADRs in a codebase. Use when asked to "write an ADR", "document this decision", "architecture decision record", "why did we choose X over Y", or "we need a record of this choice". Do NOT use for: general documentation writing — ADRs are specifically for significant architecture decisions.

Turns raw client requirements into an IEEE 830 software requirements specification through structured clarification and gap analysis.

Document architectural decisions in standardized ADR format. This skill should be used when making significant technical decisions, choosing between approaches, establishing patterns, or when other skills (create-plan, implement-plan, brainstorm) identify decisions that need documentation. Triggers on "document decision", "create ADR", "architectural decision", or automatically when invoked by other skills during planning and implementation.

Generates a candid improvement report for a software requirements specification, covering deferred features, technical risks, FR refinement suggestions, NFR gaps, validation warnings, and process recommendations.

Guides a structured software requirements specification workflow from topic intake through brainstorming, spec writing, planning, review, SRS generation, validation, and improvement reporting.

Generates a candid improvement report for a software requirements specification, covering deferred features, technical risks, FR refinements, NFR gaps, validation warnings, and process recommendations.

An ADR records one decision at the moment it is made, with the information that