Skip to content
Skills Library
Management & product · Writing

documentation

/documentation

Use when writing or structuring software specifications, requirements documents, and architecture decision records. Covers PRDs, TRDs, BRDs, ADRs, RFCs, and executable spec formats. USE FOR: choosing requirements document types, documentation strategy, specification templates, combining written specs with executable tests, architecture decision documentation DO NOT USE FOR: specific document formats (use prd, trd, brd, adr, rfc, gherkin, gauge sub-skills), diagramming (use diagramming sub-skills)

Licence
MIT
Last repository change
09.06.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
133
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 09.06.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when writing or structuring software specifications, requirements documents, and architecture decision records. Covers PRDs, TRDs, BRDs, ADRs, RFCs, and executable spec formats. USE FOR: choosing requirements document types, documentation strategy, specification templates, combining written specs with executable tests, architecture decision documentation DO NOT USE FOR: specific document formats (use prd, trd, brd, adr, rfc, gherkin, gauge sub-skills), diagramming (use diagramming sub-skills)

Original author description

Use when writing or structuring software specifications, requirements documents, and architecture decision records. Covers PRDs, TRDs, BRDs, ADRs, RFCs, and executable spec formats. USE FOR: choosing requirements document types, documentation strategy, specification templates, combining written specs with executable tests, architecture decision documentation DO NOT USE FOR: specific document formats (use prd, trd, brd, adr, rfc, gherkin, gauge sub-skills), diagramming (use diagramming sub-skills)

How it works

  1. Overview
  2. Document Types
  3. Document Flow
  4. Best Practices
Original SKILL.md headings · 60 lines, 352 words
SKILL.md preview
---
name: documentation
description: |
    Use when writing or structuring software specifications, requirements documents, and architecture decision records. Covers PRDs, TRDs, BRDs, ADRs, RFCs, and executable spec formats.
    USE FOR: choosing requirements document types, documentation strategy, specification templates, combining written specs with executable tests, architecture decision documentation
    DO NOT USE FOR: specific document formats (use prd, trd, brd, adr, rfc, gherkin, gauge sub-skills), diagramming (use diagramming sub-skills)
license: MIT
metadata:
  displayName: "Documentation & Requirements"
  author: "Tyler-R-Kendrick"
compatibility: claude, copilot, cursor
references:
  - title: "Architectural Decision Records"
    url: "https://adr.github.io/"
  - title: "Cucumber — Gherkin Reference"
    url: "https://cucumber.io/docs/gherkin/reference/"
---

# Documentation & Requirements

## Overview
Software specifications capture the "what" and "why" before implementation addresses the "how." Well-structured requirements documents, architecture decisions, and executable specs reduce ambiguity, align stakeholders, and create verifiable acceptance criteria.

## Document Types

### Requirements Documents
| Type | Audience | Focus |
|------|----------|-------|
| **PRD** (Product Requirements) | Product + Engineering | Features, user stories, success metrics |
| **TRD** (Technical Requirements) | Engineering | Architecture, APIs, data models, constraints |
| **BRD** (Business Requirements) | Business + Leadership | ROI, market need, business objectives |

### Architecture Documents
| Type | Audience | Focus |
|------|----------|-------|
| **ADR** (Architecture Decision Record) | Engineering | Single decision with context and consequences |
| **RFC** (Request for Comments) | Engineering + Stakeholders | Proposed change seeking feedback |

### Executable Specifications
| Type | Audience | Focus |
|------|----------|-------|
| **Gherkin** (Given/When/Then) | QA + Product + Engineering | Acceptance criteria as executable tests |
| **Gauge** (Markdown specs) | QA + Engineering | Free-form test specifications in Markdown |

## Document Flow

```
Business Need
    │
    ▼
  BRD ──► "Should we build this?"
    │
    ▼
  PRD ──► "What are we building?"
    │
    ├──► ADR ──► "Why did we choose X over Y?"
    │
    ▼
  TRD ──► "How do we build it?"
    │
    ├──► RFC ──► "Proposing approach Z for feedback"
    │
    ▼
  Gherkin / Gauge ──► "How do we verify it works?"
    │
    ▼
  Implementation + Automated Tests
```

## Best Practices
- Write the PRD before the TRD — define what you're building before deciding how to build it.
- Use ADRs for every significant architecture decision — they're short, structured, and invaluable for future developers.
- Make specifications executable where possible — Gherkin and Gauge connect written specs directly to automated tests.
- Keep documents close to the code in the same repository so they evolve together.
- Use lightweight templates rather than heavyweight processes — a short, focused ADR beats a 50-page design doc nobody reads.
- Review specs before implementation, not after — specifications are cheapest to change when they're still text.
Files in this package (133)
  • AGENTS.md 2 KB
  • README.md 2 KB
  • SKILL.md 3 KB
  • metadata.json 1 KB
  • adr/AGENTS.md 15 KB
  • adr/README.md 1 KB
  • adr/SKILL.md 16 KB
  • adr/metadata.json 1 KB
  • adr/rules/_sections.md 2 KB
  • adr/rules/_template.md 1 KB
  • adr/rules/adr-be-honest-about-consequences.md 1 KB
  • adr/rules/adr-include-decision-drivers.md 1 KB
  • adr/rules/adr-keep-adrs-short.md 1 KB
  • adr/rules/adr-link-adrs-to-each-other.md 1 KB
  • adr/rules/adr-never-delete-adrs.md 1 KB
  • adr/rules/adr-number-sequentially.md 1 KB
  • adr/rules/adr-review-adrs-in-pull-requests.md 1 KB
  • adr/rules/adr-revisit-adrs-periodically.md 1 KB
  • adr/rules/adr-store-adrs-in-the-repository.md 1 KB
  • adr/rules/adr-use-a-consistent-template.md 1 KB
  • adr/rules/adr-use-active-voice-in-the-decision-section.md 1 KB
  • adr/rules/adr-write-adrs-at-decision-time.md 1 KB
  • brd/AGENTS.md 16 KB
  • brd/README.md 1 KB
  • brd/SKILL.md 17 KB
  • brd/metadata.json 1 KB
  • brd/rules/_sections.md 2 KB
  • brd/rules/_template.md 1 KB
  • brd/rules/brd-always-include-a-do-nothing-alternative.md 1 KB
  • brd/rules/brd-be-honest-about-risks.md 1 KB
  • brd/rules/brd-get-formal-sign-off.md 1 KB
  • brd/rules/brd-identify-all-stakeholders-early.md 1 KB
  • brd/rules/brd-keep-it-business-focused.md 1 KB
  • brd/rules/brd-lead-with-the-executive-summary.md 1 KB
  • brd/rules/brd-plan-for-post-launch-measurement.md 1 KB
  • brd/rules/brd-quantify-everything-possible.md 1 KB
  • brd/rules/brd-review-with-finance.md 1 KB
  • brd/rules/brd-separate-business-requirements-from-product-requirements.md 1 KB
  • brd/rules/brd-use-a-consistent-format.md 1 KB
  • brd/rules/brd-validate-assumptions-explicitly.md 1 KB
  • gauge/AGENTS.md 13 KB
  • gauge/README.md 1 KB
  • gauge/SKILL.md 14 KB
  • gauge/metadata.json 1 KB
  • gauge/rules/_sections.md 1 KB
  • gauge/rules/_template.md 1 KB
  • gauge/rules/gauge-externalize-large-data-sets.md 1 KB
  • gauge/rules/gauge-integrate-with-ci-cd.md 1 KB
  • gauge/rules/gauge-keep-steps-atomic.md 1 KB
  • gauge/rules/gauge-run-specs-in-parallel.md 1 KB
  • gauge/rules/gauge-tag-consistently.md 1 KB
  • gauge/rules/gauge-use-concepts-to-build-a-domain-vocabulary.md 1 KB
  • gauge/rules/gauge-use-context-steps-for-shared-setup.md 1 KB
  • gauge/rules/gauge-use-teardown-steps-for-cleanup.md 1 KB
  • gauge/rules/gauge-validate-specs-regularly.md 1 KB
  • gauge/rules/gauge-write-specs-as-documentation-first.md 1 KB
  • gherkin/AGENTS.md 14 KB
  • gherkin/README.md 1 KB
  • gherkin/SKILL.md 15 KB
  • gherkin/metadata.json 1 KB
  • gherkin/rules/_sections.md 2 KB
  • gherkin/rules/_template.md 1 KB
  • gherkin/rules/gherkin-avoid-conjunctive-steps.md 1 KB
  • gherkin/rules/gherkin-background-should-be-short.md 1 KB
  • gherkin/rules/gherkin-keep-scenarios-independent.md 1 KB
  • gherkin/rules/gherkin-limit-steps-per-scenario.md 1 KB
  • gherkin/rules/gherkin-one-feature-per-file.md 1 KB
  • gherkin/rules/gherkin-put-feature-files-in-a-directory-structure-mirroring-the.md 1 KB
  • gherkin/rules/gherkin-reuse-steps-across-scenarios.md 1 KB
  • gherkin/rules/gherkin-tag-strategically.md 1 KB
  • gherkin/rules/gherkin-use-domain-language-not-technical-jargon.md 1 KB
  • gherkin/rules/gherkin-use-rules-gherkin-6.md 1 KB
  • gherkin/rules/gherkin-use-scenario-outline-for-data-driven-tests.md 1 KB
  • gherkin/rules/gherkin-write-declarative-not-imperative-scenarios.md 1 KB
  • prd/AGENTS.md 11 KB
  • prd/README.md 1 KB
  • prd/SKILL.md 12 KB
  • prd/metadata.json 1 KB
  • prd/rules/_sections.md 2 KB
  • prd/rules/_template.md 1 KB
  • prd/rules/prd-be-specific-about-non-goals.md 1 KB
  • prd/rules/prd-include-acceptance-criteria-for-every-user-story.md 1 KB
  • prd/rules/prd-keep-the-prd-living.md 1 KB
  • prd/rules/prd-link-to-related-documents.md 1 KB
  • prd/rules/prd-make-success-metrics-measurable.md 1 KB
  • prd/rules/prd-prioritize-ruthlessly.md 1 KB
  • prd/rules/prd-resolve-open-questions-before-development-starts.md 1 KB
  • prd/rules/prd-review-with-all-stakeholders.md 1 KB
  • prd/rules/prd-separate-functional-from-non-functional-requirements.md 1 KB
  • prd/rules/prd-start-with-the-problem-not-the-solution.md 1 KB
  • prd/rules/prd-write-user-stories-from-the-user-s-perspective.md 1 KB
  • rfc/AGENTS.md 17 KB
  • rfc/README.md 1 KB
  • rfc/SKILL.md 18 KB
  • rfc/metadata.json 1 KB
  • rfc/rules/_sections.md 2 KB
  • rfc/rules/_template.md 1 KB
  • rfc/rules/rfc-address-all-review-comments.md 1 KB
  • rfc/rules/rfc-always-include-do-nothing-as-an-alternative.md 1 KB
  • rfc/rules/rfc-be-specific-about-trade-offs.md 1 KB
  • rfc/rules/rfc-convert-accepted-rfcs-into-adrs.md 1 KB
  • rfc/rules/rfc-designate-a-decision-maker.md 1 KB
  • rfc/rules/rfc-include-a-migration-strategy.md 1 KB
  • rfc/rules/rfc-keep-rfcs-scoped.md 1 KB
  • rfc/rules/rfc-prototype-when-possible.md 1 KB
  • rfc/rules/rfc-set-a-review-deadline.md 1 KB
  • rfc/rules/rfc-start-with-the-problem-not-the-solution.md 1 KB
  • rfc/rules/rfc-use-diagrams-liberally.md 1 KB
  • rfc/rules/rfc-write-for-a-skeptical-reader.md 1 KB
  • rules/_sections.md 1 KB
  • rules/_template.md 1 KB
  • rules/documentation-keep-documents-close-to-the-code-in-the-same-repository-so.md 1 KB
  • rules/documentation-make-specifications-executable-where-possible.md 1 KB
  • rules/documentation-review-specs-before-implementation-not-after.md 1 KB
  • rules/documentation-use-adrs-for-every-significant-architecture-decision.md 1 KB
  • rules/documentation-use-lightweight-templates-rather-than-heavyweight-processes.md 1 KB
  • rules/documentation-write-the-prd-before-the-trd.md 1 KB
  • trd/AGENTS.md 16 KB
  • trd/README.md 1 KB
  • trd/SKILL.md 17 KB
  • trd/metadata.json 1 KB
  • trd/rules/_sections.md 1 KB
  • trd/rules/_template.md 1 KB
  • trd/rules/trd-define-performance-targets-with-percentiles.md 1 KB
  • trd/rules/trd-document-the-security-model-explicitly.md 1 KB
  • trd/rules/trd-include-diagrams.md 1 KB
  • trd/rules/trd-keep-it-current.md 1 KB
  • trd/rules/trd-plan-for-failure.md 1 KB
  • trd/rules/trd-record-decisions-as-adrs.md 1 KB
  • trd/rules/trd-reference-the-prd.md 1 KB
  • trd/rules/trd-review-with-the-full-engineering-team.md 1 KB
  • trd/rules/trd-specify-api-contracts-precisely.md 1 KB
  • trd/rules/trd-use-version-control.md 1 KB

Versions

RepositoryScoreLicence
This page · Tyler-R-Kendrick/agent-skills100MIT
software-combined/SC_AI100Apache-2.0
DaveSkender/Stock.Indicators100Apache-2.0
mcouthon/agents100MIT
YLfjuk/deltafold100MIT
comet-ml/opik100Apache-2.0
runwield/runwield100MIT
anthropics/knowledge-work-plugins100Apache-2.0
luocfprime/labtasker100Apache-2.0

Database snapshot: 13.11.2026 · package version 0f3b0c410b1b (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100technical-specification
    Use when the user says \"write a spec\", \"create RFC\", \"write a PRD\", or \"document this decision\". Writes technical specifications, PRDs, RFCs, and ADRs with clear structure.
  • 100prd
    Use when writing Product Requirements Documents that define what to build and why. Covers problem statements, goals/non-goals, user stories, success metrics, functional and non-functional requirements, milestones, prioritization frameworks, and the relationship to BRD and TRD.…
  • 90wise-trd-architect
    Creates and iterates on Technical Requirements Documents (TRDs) — the engineering counterpart to a PRD. Translates product requirements into architecture decisions, API contracts, data models, and implementation roadmaps. Use this skill when the user mentions TRD, technical…
  • 100gauge
    Use when writing markdown-based test specifications with the Gauge framework (ThoughtWorks). Covers specification files, scenarios, steps, concepts, data tables, tags, step implementations, data-driven testing, and reporting. USE FOR: markdown test specifications, free-form…
  • 100prd-writer
    Expert PRD (Product Requirements Document) writer for the AI era. Use when users want to create PRDs, spec documents, product specifications, feature specs, or technical requirements documents. Also use when users ask to review/improve existing PRDs, want PRD templates, need…
  • 100prd-generator
    Generate comprehensive Product Requirements Documents (PRDs) for product managers. Use this skill when users ask to "create a PRD", "write product requirements", "document a feature", or need help structuring product specifications.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.