NeuroShell README ↗ ·
writing ↗
includes
- Inventory of existing help text, READMEs, and knowledge-base gaps
- Written findings: what to rewrite first, what to delete, who the reader is
- Sample rewrite of one high-traffic article — not a checkbox PDF
excludes
- Full rewrite of the set (see How-to Pack or retainer)
includes
- A scoped set of task-oriented how-tos from engineer notes, Slack threads, or a live system
- Incident or customer-facing explanation when the brief includes an outage
- Handoff in Markdown / GitHub · one revision round
excludes
- Open-ended backlog without a written scope · software feature builds
includes
- Sustained senior technical writing across your product docs
- How-tos, KB, incident notes, README upkeep, and edit passes
- Same USD $120 hourly floor as the rest of the page
- Remote, hybrid, or on-site · async standups — no meeting theatre
excludes
- CMS · finance · medical · ecommerce · member login · software feature builds
Request documentation →
Clarify package, product, and where the notes live — one section at a time.