scribe

Write and update markdown artifacts within predefined directory scopes.

Updated Jul 21, 2026

Search Tags:#documentation #writing #markdown #file management #artifacts

Ready to run

npx skills add https://github.com/roborew/opencode --skill scribe-roborew

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scribe
Source: https://github.com/roborew/opencode/tree/main/skills/scribe
Command: npx skills add https://github.com/roborew/opencode --skill scribe-roborew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the writing and updating of markdown files in specific, approved directories, ensuring consistency and adherence to project structure.

Core Features & Use Cases

Artifact Creation: Generates new markdown files for plans, changelogs, guides, and architecture documentation.
Content Updates: Modifies existing markdown files with new information.
Use Case: After an architect agent drafts a new feature plan, the scribe skill can be invoked to write this plan to .plan/feature.new-login-flow.md.

Quick Start

Use the scribe skill to create a new file at .plan/feature.user-auth.md with the content 'This is the plan for the user authentication feature.'.

Frequently Asked Questions about scribe

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

FAQPage Schema

How do I automate writing markdown documentation to specific project directories?▼

You can automate writing markdown documentation to specific directories by routing file creation requests through predefined directory scopes, ensuring new artifacts are only generated in approved paths.

Can I update existing markdown files without creating new documentation artifacts?▼

Yes, you can update existing markdown files by specifying the explicit file path, allowing you to modify current documentation content while enforcing adherence to allowed write locations.

What is the best way to enforce strict directory paths for generated markdown plans?▼

Enforcing strict directory paths for generated markdown plans is achieved by validating explicit paths or routing tuples against predefined allowed scopes before writing any documentation artifacts.

Does this markdown file management approach support routing tuples for artifact creation?▼

Yes, this markdown file management approach supports artifact routing tuples, enabling precise creation and updating of documentation files based on structured path definitions.

When should I use predefined directory scopes for writing markdown documentation?▼

You should use predefined directory scopes for writing markdown documentation when you need to maintain project structure consistency and prevent file artifacts from being written to unauthorized locations.

Are there limitations on where markdown artifacts can be created?▼

Yes, a key limitation is that markdown artifacts cannot be created outside of the strict, predefined allowed write locations, meaning all explicit paths must be approved beforehand.