scribe

Records decisions, sessions, and findings into a structured project knowledge base.

Updated Aug 19, 2025
One-click install
npx skills add https://github.com/loganmancuso-scout/dotfiles --skill scribe-loganmancuso-scout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scribe
Source: https://github.com/loganmancuso-scout/dotfiles/tree/main/dot_pi/agent/skills/scribe
Command: npx skills add https://github.com/loganmancuso-scout/dotfiles --skill scribe-loganmancuso-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Important architectural decisions, debugging findings, and session outcomes get lost when work ends, forcing teams to rediscover context repeatedly. This Skill captures that knowledge into a persistent, structured knowledge base with consistent formats. ## Core Features & Use Cases - Documentation Mode: Records decisions as ADRs, work summaries as session files, debugging efforts as investigation notes, and operational steps into runbooks, gotchas, and context.md files. - Scratch Mode: Provides a temporary workspace for brainstorming, planning, and offloading context when the working window grows, with a defined path to promote scratch notes into polished documentation. - Structured Conventions: Enforces frontmatter tags (type/, audience/, topic/), markdown style standards, and project identity resolution via git root detection. - Use Case: After finishing a database migration session, ask the agent to record the work — it creates a dated session file, updates context.md links, and logs any discovered gotchas. ## Quick Start Record today's completed work on the database migration as a session entry in the project knowledge base.

Frequently Asked Questions about scribe

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

FAQPage Schema
How do I record an architectural decision in a knowledge base?

Invoke the skill after a significant decision and it creates a dated ADR file under decisions/YYYY-MM-DD-slug.md with Status, Context, Decision, Rationale, Alternatives, and Consequences sections, then links it from context.md.

How do I document a completed work session for future reference?

Provide a summary of what was built and learned; the skill writes a session file named sessions/YYYY-MM-DD[-topic].md with Goal, Work Done, Findings, and Next Steps sections, and updates the Recent Sessions list in context.md.

Can I use the knowledge base as a scratch workspace for planning?

Yes, scratch mode lets you write messy exploratory notes prefixed with SCRATCH- in sessions/, investigations/, or inbox/ directories. Scratch files can later be promoted into proper session or decision files, then deleted.

Does the scribe skill modify source code files?

No, in documentation mode it only writes to knowledge base markdown files and README files. It explicitly does not touch source files, configs, or manifests, and redirects design or implementation requests back to normal session mode.

What happens if the knowledge base files do not exist yet?

The skill reads the corresponding template from ~/Documents/Notes/templates/ (context, runbook, gotchas, session, ADR, or investigation templates), copies it to the project knowledge base path, and populates it with project-specific content.