forge-security

Generate a traceable security checklist from task or slice plans.

3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/vh2224/forge-agent --skill forge-security-vh2224
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-security
Source: https://github.com/vh2224/forge-agent/tree/main/skills/forge-security
Command: npx skills add https://github.com/vh2224/forge-agent --skill forge-security-vh2224

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a focused approach to derive security requirements directly from task or slice plans, ensuring that only in-scope areas are assessed and that each item is traceable to plan content.

Core Features & Use Cases

  • Active-domain mapping that reads the plan to determine which security domains apply.
  • Blocker vs Check tier classification to prioritize verification work and avoid over-automation.
  • Generates a concrete Security Checklist document (e.g., T##-SECURITY.md) with explicit items, risk levels, and rationale.
  • Use Case: A plan for a new authentication flow yields a domain-specific checklist confirming token handling, request validation, and error safety.

Quick Start

Analyze the active plan and generate a tailored security checklist for the detected domains.

Frequently Asked Questions about forge-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a security checklist from a task plan?▼

Generating a security checklist from a task plan involves identifying active security domains like API, data handling, and transport. It then produces a traceable checklist with concrete acceptance criteria and risk levels for each identified requirement.

What is active-domain mapping for security requirements?▼

Active-domain mapping for security requirements is the process of reading a task plan to determine which specific security domains apply. It ensures only explicitly mentioned areas are assessed, preventing over-automation and keeping the checklist focused.

How do I prioritize security verification tasks from a slice plan?▼

Prioritize security verification tasks by classifying items into Blocker versus Check tiers. This classification helps focus verification work on critical risks first, ensuring traceability directly back to the slice plan content.

Can I use a security checklist for authentication flow planning?▼

Yes, you can generate a security checklist for authentication flow planning. It applies to auth concerns by confirming token handling, request validation, and error safety based directly on the authentication flow plan content.

Does automated security checklist generation work without explicit plan details?▼

Automated security checklist generation does not work without explicit plan details. It activates only domains that the plan explicitly mentions, requiring every checklist item to be directly supported by plan content to ensure traceability.