scribe-technical-documentation

Stars0

Forks0

UpdatedJuly 14, 2026 at 03:05

Write README, API, architecture, operator, and developer documentation from verified repository and engineering evidence.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

lebobo88

lebobo88/orchestrator

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	scribe-technical-documentation
description	Write README, API, architecture, operator, and developer documentation from verified repository and engineering evidence.
user-invocable	false

Technical documentation

Use with scribe-core for README, API, architecture, installation, operation, and troubleshooting documents.

Trace every behavior, command, path, and example to supplied engineering evidence or current repository files.
State prerequisites, supported scope, verification commands, error limits, and operational consequences without implying unverified behavior.
Prefer task-oriented headings and short examples with expected outcomes. Preserve compatibility constraints and call out deliberately unsupported workflows.
Validate links, paths, command names, and code fences against the target repository before finishing.
For browser UI documentation, preserve the no-native-dialog invariant: document app-owned modal or inline-feedback behavior, keyboard/focus expectations, and deterministic verification. Do not document native browser dialogs as supported behavior.

More from this repository

same repository

browser-validator-core

lebobo88/orchestrator

Screenshot-first visual end-to-end validation policy for browser-rendered UI and webview jobs after verifier approval.

2026-07-180

build

lebobo88/orchestrator

Default engineering workflow. Classify a technical request, route it through the native T1/T2/T3 engineering fleet, and return only independently verified completion to the orchestrator.

2026-07-180

claude-operations

lebobo88/orchestrator

Safely operate Claude Code's opt-in advanced capabilities—sessions, worktrees, agent teams, Skills, MCP, plugins, hooks, Channels, schedules, goals, and Agent SDK integrations—when the user explicitly asks for one. Do not use for an ordinary build request.

2026-07-170

cross-vendor-judging

lebobo88/orchestrator

Routes selective local Codex plan, code, verification, and visual judgment with evidence-backed blocking and strict cost caps.

2026-07-170

design-core

lebobo88/orchestrator

Shared evidence, accessibility, context, and handoff rules for the local design-agent fleet.

2026-07-170

design-direction

lebobo88/orchestrator

Produces contextual creative theses and bounded visual directions without generic model defaults.

2026-07-170

name	scribe-technical-documentation
description	Write README, API, architecture, operator, and developer documentation from verified repository and engineering evidence.
user-invocable	false

Technical documentation

Use with scribe-core for README, API, architecture, installation, operation, and troubleshooting documents.

Trace every behavior, command, path, and example to supplied engineering evidence or current repository files.
State prerequisites, supported scope, verification commands, error limits, and operational consequences without implying unverified behavior.
Prefer task-oriented headings and short examples with expected outcomes. Preserve compatibility constraints and call out deliberately unsupported workflows.
Validate links, paths, command names, and code fences against the target repository before finishing.
For browser UI documentation, preserve the no-native-dialog invariant: document app-owned modal or inline-feedback behavior, keyboard/focus expectations, and deterministic verification. Do not document native browser dialogs as supported behavior.