Security-Requirement Review

When to Use

• Use this Skill when the work needs evidence-bounded analysis of security objectives, testability, trace links, acceptance conditions, and evidence gaps.
• Use it when input is incomplete but a reviewable draft with assumptions and gaps is still useful.
• Use it when static security evidence must remain separate from planned validation and completed execution.

Output Format Options

• Default to Markdown organized by security risk, evidence, and priority.
• If the user asks for a table, CSV, JSON, or ticket format, preserve the same finding fields and evidence states.
• Confirm the schema, enum values, and required fields before feeding the output to automation.

How to Use