skills.rest
Yukine5377
Yukine5377COMMUNITY
Explore all skills by this author →
GitHub

po-srs

Develop a comprehensive Software Requirements Specification document from project context.

Updated Apr 12, 2026
Search Tags:#architecture#specification#requirements#srs#technical-writing#product-management
One-click install
npx skills add https://github.com/Yukine5377/common --skill po-srs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: po-srs
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/po-srs
Command: npx skills add https://github.com/Yukine5377/common --skill po-srs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hướng dẫn viết Software Requirements Specification (SRS) theo quy trình của một Senior Product Owner phối hợp với Technical Lead. Sử dụng skill này khi người dùng muốn: viết đặc tả kỹ thuật cho hệ thống, định nghĩa functional và non-functional requirements ở mức technical, mô tả tech stack và architecture, hoặc chuẩn bị tài liệu cho dev team bắt đầu implementation.

Core Features & Use Cases

  • Hướng dẫn xây dựng SRS đầy đủ và chuẩn mực cho dự án.
  • Cung cấp khuôn mẫu cho các phần: Header, Introduction, Tech Stack, Architecture, Requirements, Interfaces, Deployment.
  • Use Case: Ví dụ viết SRS cho một hệ thống quản lý tồn kho từ PRD tới triển khai cho Dev Team.

Quick Start

Tạo một SRS hoàn chỉnh cho dự án hiện tại theo các phần đã định.

Frequently Asked Questions about po-srs

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

FAQPage Schema
How do I write a Software Requirements Specification document from a PRD?▼

A comprehensive SRS bridges PRD and Dev by detailing tech stack, system architecture, functional and non-functional requirements, interfaces, and database schema to guide the development team.

What sections should be included in an SRS document for a dev team handoff?▼

An SRS document for dev team handoff should include a header, introduction, tech stack, architecture, functional and non-functional requirements, interfaces, database schema, deployment, and reference materials.

How do I define non-functional requirements at a technical level for system architecture?▼

Defining technical non-functional requirements involves specifying system architecture constraints and performance metrics within the SRS, ensuring the technical specification aligns with the product's operational demands.

Can I use this approach to generate technical specifications for an inventory management system?▼

Yes, you can generate technical specifications for systems like inventory management by detailing the architecture, database schema, and functional requirements from the initial PRD to final deployment.

What is the best way to structure a technical specification bridging product management and development?▼

The best way to structure a technical specification bridging product management and development is using a standardized SRS format covering architecture, interfaces, and deployment to ensure implementation alignment.

Related Skills

Explore More Product & Management Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
Eigo-Mt-FujiEigo-Mt-Fuji

database-schema-designer

Design database schemas, ER diagrams, and DDL for relational and NoSQL databases.

Community
Advanced
VSF-QC-TTSVSF-QC-TTS

common-architecture-diagramming

Standardize architecture diagrams using C4 and UML models with Mermaid syntax.

Official
Intermediate
josavicentevwjosavicentevw
1

product-owner

Defines requirements and manages Agile backlogs for product teams.

Community
Basic