Route documentation input to product, architecture, or implementation files.
npx skills add https://github.com/alexanderguy/skills --skill scribe-alexanderguy
Please help me install this Agent Skill. Skill: scribe Source: https://github.com/alexanderguy/skills/tree/main/skills/scribe Command: npx skills add https://github.com/alexanderguy/skills --skill scribe-alexanderguy
Scribe helps you turn messy or partial notes into complete, consistent documentation by automatically routing new input to the right abstraction level and then identifying what’s missing.
Use the scribe skill to update the right doc types from your latest notes by saying: “Scribe, incorporate the following details into our docs and ask what’s missing: [paste your notes].”
High-intent search queries and answers about installing and using this skill.
To ensure documentation completeness and consistency, this skill performs cross-document consistency checks after routing new input. It detects gaps between product, architecture, and implementation docs, then uses interactive questioning to resolve ambiguity and collect missing details.
To structure product requirements and architecture documentation from messy notes, this skill decomposes ambiguity through interactive interviewing. It takes partial input, determines the correct abstraction level, and updates the appropriate documentation file with targeted follow-up questions.
You do not need to manually create product, architecture, and implementation docs beforehand. This skill searches for existing PRODUCT.md, ARCHITECTURE.md, and IMPLEMENTATION.md files in the root or docs/ directory, and automatically creates sensible default files if they are missing.
The best way to maintain cross-document consistency across product requirements and system design files is to use a skill that actively checks for alignment after updates. It analyzes new input, routes it to the correct file, and identifies completeness gaps across the entire documentation structure.
s3nex-comConvert raw notes into structured Product Requirements Documents.
Andy-HNUSynchronize Markdown docs with shipped changes after PR merges.
TrogonStackParse product overview documentation to generate Feature Requirements Document stubs.
yakksiekGenerate schema-conformant PRDs from shaping notes with template auto-routing.
