Scribe

Generate PRDs, SRSs, HLDs, LLDs, and test specifications.

68|14|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/simota/agent-skills --skill scribe-simota
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Scribe
Source: https://github.com/simota/agent-skills/tree/main/scribe
Command: npx skills add https://github.com/simota/agent-skills --skill scribe-simota

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of essential technical documentation, transforming ideas and decisions into structured, implementation-ready documents and ensuring clarity and consistency in project communication.

Core Features & Use Cases

  • Technical Document Generation: Creates PRDs, SRSs, HLDs, LLDs, and test specifications.
  • Checklist Creation: Generates implementation and review checklists.
  • Use Case: When a new feature is defined, use Scribe to generate a comprehensive PRD outlining user stories, functional requirements, and acceptance criteria, followed by an SRS detailing technical specifications and NFRs.

Quick Start

Use the scribe skill to create a PRD for the new user login feature.

Frequently Asked Questions about Scribe

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

FAQPage Schema
How do I generate a PRD with functional requirements and acceptance criteria for a new feature?

To generate a PRD, you provide the feature intent to the documentation writer, which structures user stories, functional requirements, and acceptance criteria into an implementation-ready document using standardized templates.

What is the best way to create technical specifications like SRS and HLD for software projects?

The best way to create technical specifications like SRS and HLD is to use an automated technical writing tool that drafts requirements, facilitates review, and finalizes structured artifacts for project communication.

Can I generate implementation and review checklists alongside software requirements specifications?

Yes, you can generate implementation and review checklists alongside an SRS, as the documentation process supports creating both detailed technical specifications and validation checklists to ensure implementation readiness.

Do I need standardized templates to write low level design documents, or can they be generated automatically?

Low level design documents can be generated automatically by understanding project intent and structuring content with standardized templates, eliminating the need to manually build formatting structures from scratch.

When do I need to generate test specifications and non functional requirements for a software project?

You need to generate test specifications and non functional requirements when transitioning from high level design to implementation readiness, ensuring technical specifications and validation criteria are finalized before development.

What distinguishes automated technical documentation generation from manual specification writing?

Automated technical documentation generation transforms ideas and decisions directly into structured documents through intent understanding and template standardization, whereas manual specification writing requires formatting and drafting each requirement by hand.