requirements-engineering
Runs the requirements-engineering phase — the first SDLC step, upstream of design. Through a thorough, area-by-area interview it elicits and specifies the complete requirements for a new application, proactively enumerating the standard sub-requirements for each capability area (for authentication: sign-up, sign-in, verification, password reset, logout) plus all non-functional requirements. Produces a structured SRS (ISO/IEC/IEEE 29148 lineage) with functional requirements in EARS syntax or classic "shall" statements, in markdown, a separate use-case document, and a requirements traceability matrix. Also amends a finalized SRS — adding, updating, or removing requirements with stable IDs. Use at the start of a project before architecture and UX, or when changing existing requirements. Trigger on "gather requirements", "write an SRS", "requirements engineering", "specify the requirements", "add a requirement", or "update the requirements". Saves progress incrementally so long sessions ca
zeeshanhanif · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add zeeshanhanif/agentic-sdlc-kit --skill requirements-engineering技能说明
name: requirements-engineering description: >- Runs the requirements-engineering phase — the first SDLC step, upstream of design. Through a thorough, area-by-area interview it elicits and specifies the complete requirements for a new application, proactively enumerating the standard sub-requirements for each capability area (for authentication: sign-up, sign-in, verification, password reset, logout) plus all non-functional requirements. Produces a structured SRS (ISO/IEC/IEEE 29148 lineage) with functional requirements in EARS syntax or classic "shall" statements, in markdown, a separate use-case document, and a requirements traceability matrix. Also amends a finalized SRS — adding, updating, or removing requirements with stable IDs. Use at the start of a project before architecture and UX, or when changing existing requirements. Trigger on "gather requirements", "write an SRS", "requirements engineering", "specify the requirements", "add a requirement", or "update the requirements". Saves progress incrementally so long sessions can resume.
Requirements Engineering
This skill produces the traditional, structured requirements specification that sits at the very front of the SDLC — upstream of architecture and UX. It is deliberately a detail phase: its job is to capture every requirement comprehensively, so that the documents it produces become the single source of truth the design and planning skills downstream consume.
Two principles define it:
-
Exhaustive enumeration, not transcription. When a capability area comes up, the skill does not merely record what the user mentions. It proactively proposes the full set of standard sub-requirements for that area and has the user confirm, extend, or remove them. "User authentication" is never one line — it expands into sign-up, sign-in, email verification, forgot password, reset password, change password, logout, session expiry, account lockout, rate limiting, and so on. The
requirement-catalog.mdreference is the engine for this. The same discipline applies to non-functional requirements. -
Structured and traditional. The output is a formal SRS in the ISO/IEC/IEEE 29148 (IEEE 830) lineage — numbered, uniquely-identified, testable requirements — not an agile backlog. Whatever the SRS calls a unit (function / feature) is fine; epic and feature slicing is deliberately deferred to the downstream implementation-planning skill. This skill owns the problem space, comprehensively.
Because a full requirements interview is long, the skill checkpoints its work
incrementally and can resume after an interruption — see Phase 0 and
references/checkpointing.md.
Inputs
This is the first skill in the pipeline, so it has no upstream document to consume — it elicits from the user. If the user has an existing brief, notes, or partial requirements, ingest them first and treat them as raw input to confirm and expand, not as finished requirements.
Outputs
Three files (three logical documents), all markdown, written to docs/.
docs/srs.md— the comprehensive SRS (the source of truth downstream skills read). Vision & scope, user characteristics, constraints, assumptions, glossary, functional requirements, and non-functional requirements all live here as structured sections.docs/use-cases.md— detailed textual use-case specifications plus a Mermaid use-case diagram (separate document, use-case-centric; no user stories).docs/rtm.md— the Requirements Traceability Matrix (markdown table).
Word/PDF output is out of scope — markdown is the deliverable. Users who want a Word version can convert it themselves (e.g., with pandoc); this skill does not own that.
Plus working files that are not deliverables: docs/.requirements-progress.md
(the progress tracker), and the incrementally-built srs.md / use-cases.md
drafts themselves (which become deliverables 1 and 2 once finalized).
Workflow
Phase 0 — Mode detection (always first)
Before anything else, look for docs/.requirements-progress.md and docs/srs.md
and read references/checkpointing.md. Determine which of three modes applies
by combining what's on disk with the user's intent:
- Fresh start — no SRS and no tracker. Create the progress tracker and the SRS skeleton, then begin Phase 1.
- Resume — a tracker exists with
pending/in-progressareas (the interview was interrupted). Read both files, summarize what's captured and what remains, and continue from the first pending area. - Amendment — a finalized SRS exists (tracker shows no pending work, or is marked finalized) and the user wants to change requirements. Switch to amendment handling (Phase A) instead of resuming or restarting.
Detection is automatic — the user passes no special flag. The finalized SRS on disk is the precondition; the user's plain-language intent disambiguates ("add a requirement", "update FR-AUTH-007", "remove…" → amendment; "spec a new project" → fresh; "what does the SRS say…" → just answer). Two firm rules:
- Resume beats amend. If the interview is unfinished and the user asks to add something new, finish the pending areas first, then handle the new request — amending a half-specified SRS invites inconsistency.
- When an SRS exists and intent is ambiguous, confirm before acting — never silently restart. A bare invocation against a finalized SRS gets a short question ("There's a finalized SRS here — v1.2, 47 functional / 19 non-functional. Amend it, ask about it, or start a new one?"), not a guess. The expensive failure is wiping or duplicating a finalized SRS; one cheap question prevents it.
Phase 1 — Frame and scope
Establish the foundation: the product's purpose and vision, business goals and success metrics, the primary stakeholders, the user classes/personas, and the overall scope (what's
阅读完整来源 ↗