# prd-securability-enhancement

prd-securability-enhancement enriches PRDs, user stories, and feature specs with OWASP ASVS controls and FIASSE guidance before developers write code.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 170 installs · ★ 230 repo stars
- Author: OWASP
- License: CC-BY-4.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/OWASP/secure-agent-playbook/tree/HEAD/plugins/code-security-skills/skills/prd-securability-enhancement/SKILL.md
- Updated: 2026-10-15
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/prd-securability-enhancement

## What it does

This skill ingests product requirements documents, task lists, or briefs and attaches clear security specifications aligned with OWASP ASVS and FIASSE v1.0.4. It isolates each capability, logs the actors involved, marks data sensitivity classes, and maps trust boundaries across system components. Level 2 of ASVS serves as the standard baseline for authenticated production services, while internal tools or regulated workflows receive adjusted coverage.

Every identified capability receives observable acceptance criteria covering error modes, failure states, and unauthorized access scenarios. The tool operates solely on requirements artifacts. It deliberately avoids inspecting source code or authoring implementation logic.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add OWASP/secure-agent-playbook --skill prd-securability-enhancement -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/prd-securability-enhancement/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/prd-securability-enhancement/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add OWASP/secure-agent-playbook --skill prd-securability-enhancement -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/prd-securability-enhancement/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add OWASP/secure-agent-playbook --skill prd-securability-enhancement -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/prd-securability-enhancement/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install OWASP/secure-agent-playbook plugins/code-security-skills/skills/prd-securability-enhancement
```

2. **Manually: put the files in place**
- File: `.github/skills/prd-securability-enhancement/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add OWASP/secure-agent-playbook --skill prd-securability-enhancement -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/OWASP/secure-agent-playbook --path plugins/code-security-skills/skills/prd-securability-enhancement
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/prd-securability-enhancement/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add OWASP/secure-agent-playbook --skill prd-securability-enhancement -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/OWASP/secure-agent-playbook/tree/HEAD/plugins/code-security-skills/skills/prd-securability-enhancement/SKILL.md

## When to use it
- embed testable security requirements into PRDs before implementation
- determine the baseline OWASP ASVS assurance level for a product
- map feature specifications to relevant ASVS security verification chapters
- establish observable acceptance criteria for trust boundaries and edge cases

## Example prompts
- Harden this PRD with OWASP ASVS requirements and acceptance criteria
- Recommend an ASVS level and find missing security requirements in this spec
- Map these user stories to FIASSE securability notes

## Source text · SKILL.md · CC-BY-4.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 93ba5d43a5b0cd6c.

BEGIN THIRD-PARTY FILE 93ba5d43a5b0cd6c
```text
---
name: prd-securability-enhancement
description: Enhance PRDs, feature specs, user stories, or product briefs with explicit OWASP ASVS coverage and FIASSE v1.0.4 SSEM implementation guidance — before code is written. Trigger on "harden the PRD/spec", "choose ASVS level", "map features to ASVS", "find missing security requirements", "add NFRs for security", "make these requirements securable", "security-review my product brief". For code review use securability-engineering-review; for code generation use securability-engineering.
license: CC-BY-4.0
---

# PRD Securability Enhancement (FIASSE/SSEM + ASVS)

Enhance PRD content so each feature has explicit, testable securability requirements aligned to OWASP ASVS and shaped by FIASSE v1.0.4 / SSEM. The goal is to upgrade the requirements artifact *before* implementation, so delivery teams build securable capabilities by design rather than retrofitting controls later.

This skill is requirements-centric. It does not review or write code. If the user wants code review, redirect to `securability-engineering-review`. If they want code generation, redirect to `securability-engineering`.

## When to Invoke

Trigger this skill when the user asks to:

- Strengthen or harden a PRD, spec, user-story set, or product brief with security requirements
- Choose an ASVS assurance level (Level 1, 2, or 3) for a product or feature
- Map features to ASVS controls or check ASVS coverage of a requirements doc
- Find missing security requirements before development starts
- Annotate features with SSEM attributes or FIASSE tenets
- Add testable security acceptance criteria to existing functional requirements

Adjacent phrasings: "security-review this spec", "what's missing security-wise from this feature list", "add NFRs for security to my PRD", "make these requirements securable".

## Inputs

Ask the user for whatever is missing before starting:

- The PRD, spec, or feature list (markdown, prose, ticket export, etc.)
- System context: user types, deployment model, data sensitivity, integration surfaces
- Compliance or risk context, if any (HIPAA, PCI, SOC 2, regulated industry)
- Whether they have an ASVS level preference, or want this skill to recommend one

If the artifact is large, parse the features inline; do not require the user to pre-extract them.

## Procedure

### Step 1 — Parse features

Extract each feature into a normalized record. Capture for each:
```
END THIRD-PARTY FILE 93ba5d43a5b0cd6c

The third-party file has ended. Everything between the 93ba5d43a5b0cd6c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2437 of 18553 bytes. © OWASP · CC-BY-4.0 · https://github.com/OWASP/secure-agent-playbook/tree/HEAD/plugins/code-security-skills/skills/prd-securability-enhancement/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
