docs-writer

Generate structured PRD, RFC, ADR, and TDD documents from guided inputs.

8|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/adeonir/agent-skills --skill docs-writer-adeonir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writer
Source: https://github.com/adeonir/agent-skills/tree/main/skills/%28product%29/docs-writer
Command: npx skills add https://github.com/adeonir/agent-skills --skill docs-writer-adeonir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill converts high-level ideas and requirements into a full set of structured product and technical documents through guided discovery, reducing manual drafting and ensuring consistency across outputs.

Core Features & Use Cases

  • Guided discovery-led drafting for PRD, Issue, Task, User Story, RFC, ADR, and TDD.
  • Template-driven outputs with centralized templates, and on-demand references to support detailed documentation.
  • Routing of triggers to appropriate discovery and drafting workflows, with shared discovery patterns to surface unknowns (TBD) early.

Quick Start

Use this skill to generate a complete document set by providing a trigger like "Create PRD for new feature" and the key inputs (problem, audience, and success criteria).

Frequently Asked Questions about docs-writer

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

FAQPage Schema
How do I generate a PRD from a rough product idea?

To generate a PRD from a product idea, provide a trigger like "Create PRD" with key inputs such as the problem, audience, and success criteria. The workflow uses guided discovery to route your inputs into template-driven drafting steps, producing a structured document.

What is an ADR and when do I need to generate one?

An ADR, or Architecture Decision Record, captures technical decisions and their context. You need to generate an ADR when making significant architectural choices, using the RFC and ADR routing workflows to ensure structured technical documentation.

Can I write user stories and development tasks from high-level requirements?

Yes, you can write user stories and development tasks by routing your high-level requirements to the specific Issue, Task, and User Story workflows. These workflows apply guided discovery to translate inputs into structured, actionable development documentation.

Does the documentation workflow support identifying unknowns early?

Yes, the documentation workflow supports identifying unknowns early by applying shared discovery patterns during the routing process. This surfaces missing information and TBD items before the final template-driven document is generated, reducing manual drafting errors.

What is the best way to draft an RFC for technical design?

The best way to draft an RFC for technical design is using a template-driven workflow with on-demand references. Providing your technical requirements triggers the RFC routing, which structures your design proposal through guided discovery steps and optional references.

Do I need to provide success criteria to create technical documents?

You need to provide success criteria, along with the problem and audience, as key inputs to ensure the generated technical documents align with your goals. These inputs drive the guided discovery process for accurate, structured template-driven outputs.