harness-agent-tech-writer

Generate structured technical documentation grounded in repository context and configuration.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/baobao0303/harness --skill harness-agent-tech-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-agent-tech-writer
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-agent-tech-writer
Command: npx skills add https://github.com/baobao0303/harness --skill harness-agent-tech-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts fragmented project context and requirements into clear, structured technical documentation that agents and humans can reliably use.

Core Features & Use Cases

  • Persona-based technical writing: Operates as “Paige” to produce audience-aware documentation with strong structure and clarity.
  • Customization-driven behavior: Resolves and applies layered persona/menu/config from customize.toml and project/user override files.
  • Context loading for accuracy: Loads persistent facts and project knowledge/config to ground outputs in the repository.

Quick Start

Invoke harness-agent-tech-writer when you want to “document the codebase for onboarding so future agents can safely make changes without breaking product intent.”

Frequently Asked Questions about harness-agent-tech-writer

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

FAQPage Schema
How do I generate technical documentation from repository context for AI agents?▼

Generate technical documentation from repository context by invoking a persona-based writer that loads persistent project facts and config files. This grounds the output in your architecture, specs, and decisions, producing reader-ready docs for safe onboarding.

What is persona-based technical writing for codebase documentation?▼

Persona-based technical writing adopts a curated writer profile to produce audience-aware documentation. It resolves layered customization from config files to ensure the generated documentation maintains strong structure, clarity, and appropriate tone for human and agent readers.

How do I document architecture and specs to onboard future agents safely?▼

Document architecture and specs for future agents by loading persistent facts and project knowledge into the writer. This grounds the generated documentation in repository context, capturing validation expectations and product intent to prevent breaking changes.

Can I customize technical writing behavior with config files for different projects?▼

Customize technical writing behavior using customize.toml and project or user override files. The writer resolves layered persona, menu, and config settings from these files to drive language selection and output artifact handling for your specific project.

Does YAML frontmatter-driven discovery work for technical documentation generation?▼

YAML frontmatter-driven discovery works with technical documentation generation by satisfying metadata requirements for searchability. The generated docs include YAML frontmatter to ensure stable discovery and reliable access for AI agents operating within the repository.

What are the limitations of using a persona-based approach for knowledge curation?▼

A limitation of persona-based knowledge curation is its reliance on persistent facts and repository context accuracy. If project knowledge or config files are fragmented or outdated, the generated documentation may not fully reflect current architecture or validation expectations.