skills.rest
minhquan2904
minhquan2904COMMUNITY
Explore all skills by this author →
GitHub

srs

Generate a consolidated srs.md from proposal.md and context in openspec/changes/<name>/.

Updated Mar 27, 2026
Search Tags:#documentation#specification#requirements#srs#openspec#proposal#change-management
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill srs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: srs
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/srs
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill srs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a structured Software Requirements Specification by consolidating proposals and multi-source context into a single, ready-to-use document.

Core Features & Use Cases

  • Consolidation: Merges proposals.md with context from openspec to produce a complete SRS.
  • Context-Aware: Incorporates additional sources (Confluence/docs/code) as available following the standard mapping rules.
  • Output: Writes srs.md into openspec/changes/<name>/ for downstream design and review.

Quick Start

Place your proposal.md in openspec/changes/<name>/proposal.md, then run this skill to generate openspec/changes/<name>/srs.md.

Frequently Asked Questions about srs

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

FAQPage Schema
How do I generate a Software Requirements Specification from a project proposal?▼

To generate a Software Requirements Specification, consolidate your proposal.md and multi-source context into a structured srs.md document to establish clear project requirements before downstream design.

What is an SRS document and when do I need it for software engineering?▼

An SRS document is a detailed Software Requirements Specification that consolidates proposals and multi-source context into a ready-to-use document, needed when transitioning from project proposals to downstream design tasks.

How do I consolidate proposal content and context into a single requirements document?▼

Consolidate proposal content by aggregating proposal.md with related context from Confluence, docs, or code following standard mapping rules, producing a complete srs.md file for review and downstream design.

Does the SRS generation process work with Confluence and code documentation sources?▼

Yes, the SRS generation process incorporates additional context sources like Confluence, docs, and code as available, following standard mapping rules to merge them with your proposal.md file.

What is the best way to manage change proposals and requirements in openspec?▼

The best way to manage change proposals in openspec is to place proposal.md in the openspec/changes/<name>/ directory and generate a consolidated srs.md file to establish structured requirements for downstream review.

Why does my SRS generation fail without a proposal.md file?▼

SRS generation fails without a proposal.md file because the process requires proposal content placed in openspec/changes/<name>/proposal.md as the primary input to aggregate context and produce the final srs.md document.

Related Skills

Explore More Software Engineering Skills→
xiayu519xiayu519
63

openspec-propose

Create OpenSpec change proposals with proposal.md, design.md, and tasks.md artifacts.

Community
Advanced
projectedanxprojectedanx
1

writing-plans

Generate structured, test-driven implementation plans for software development tasks.

Community
Intermediate
mvandermeulenmvandermeulen
2

documentation-specialist

Generate, extract, and audit software documentation from Spring Boot and FastAPI codebases.

Community
Advanced
xlelibertyxleliberty

code-to-prd

Reverse-engineer codebases into Product Requirements Documents with API and model analysis.

Community
Advanced