requirement-elicitation
Requirement Elicitation
Overview
Use this skill to collect requirement evidence with traceability, confidence, and contradiction visibility.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Evidence strength rules:
references/evidence-strength-rules.md
Templates And Assets
- Evidence intake template:
assets/evidence-intake-template.csv
- Clarification question log:
assets/clarification-question-log-template.md
Inputs To Gather
- Stakeholder map and decision owners.
- Existing docs/tickets/incidents/analytics.
- Known unknowns and contested assumptions.
Deliverables
- Structured evidence set with confidence scores.
- Clarification question backlog with owners.
- Requirement candidate seeds for baseline synthesis.
Workflow
- Capture evidence in
assets/evidence-intake-template.csv. - Apply confidence/contradiction rules from
references/evidence-strength-rules.md. - Separate evidence, assumptions, and unknowns.
- Track unresolved questions in
assets/clarification-question-log-template.md. - Publish elicitation package for requirements-definition.
Quality Standard
- Evidence has source traceability and confidence labels.
- Contradictions are explicit and unresolved items are owned.
- Inputs are sufficient for canonical baseline synthesis.
Failure Conditions
- Stop when evidence depends on weak single-source claims.
- Stop when critical unknowns have no owner/due date.
- Escalate when legal/privacy constraints are unclear.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9