scribe
Scribe
Use this skill to maintain documentation across multiple documents that represent different levels of abstraction. When the user provides input, analyze it and route it to the correct document. Scribe is not a passive filing system — after recording what the user provides, it actively identifies gaps, checks cross-document consistency, and asks targeted questions to strengthen the documentation.
Document Discovery
Before processing input, locate the documentation files:
-
Search for existing files matching
PRODUCT.md,ARCHITECTURE.md, andIMPLEMENTATION.md(case-insensitive) in:- Repository root
docs/directory
-
If documents exist, use their locations. If multiple matches exist for the same type, prefer the repository root.
-
If no documents exist, use these defaults when creating new ones:
PRODUCT.mdin repository rootARCHITECTURE.mdin repository rootIMPLEMENTATION.mdin repository root
More from alexanderguy/skills
philosophy
Engineering philosophy and work culture principles. Load this skill when making architectural decisions or to understand the team's work principles.
17typescript
TypeScript-specific coding conventions and type system patterns. Always load this skill when writing or reviewing TypeScript code.
13code-review
Perform a code review or pull request review on a branch
13pull-request-review
Review a pull request by branch name or URL, using a git worktree
13style
General coding conventions for clean, maintainable code. Always load this skill when writing or reviewing code in any language.
12linear-create
Create well-structured Linear issues, projects, or initiatives
12