tech-doc

Generates technical documentation with setup guides, architecture overviews, and integration guides for development teams.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill tech-doc-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-doc
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/development/tech-doc
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill tech-doc-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development teams often lack consistent, accurate technical documentation, making onboarding slow and maintenance error-prone. This Skill generates a complete technical documentation document covering architecture, environment setup, coding patterns, testing, and deployment, gated by a human signature workflow. ## Core Features & Use Cases - Structured Documentation Generation: Produces a full technical document with architecture overview, technology stack tables, environment setup, project structure, coding patterns, testing guides, and troubleshooting sections. - Constraint Enforcement: Extracts mandatory technical and architectural constraints from the signed Software Architecture Document to guide implementation decisions. - Signature-Gated Workflow: Validates prerequisites, document ID format, and cross-references before the Technical Lead signs off, ensuring traceability. - Use Case: After the architecture phase is approved, a Technical Lead invokes this Skill to produce developer onboarding documentation that new team members can follow to set up their environment on the first attempt. ## Quick Start Ask the agent to generate the technical documentation for your project once the software architecture document and governance document are signed.

Frequently Asked Questions about tech-doc

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

FAQPage Schema
How do I generate technical documentation for a development team?▼

Invoke the tech-doc skill after the software architecture document and governance document are signed. The agent gathers project details like technology stack, repository structure, and integration points, then generates a complete Markdown document with setup guides, coding patterns, and troubleshooting sections.

What should technical documentation for developers include?▼

It should include an architecture overview, technology stack table, environment setup steps, environment variables, project structure, coding patterns with examples, testing guides, build and deployment instructions, and a troubleshooting section. This Skill generates all of these sections from a structured template.

What prerequisites are required before running this documentation skill?▼

The software-architecture-document and governance-doc must exist and be signed before this skill runs. The skill blocks execution and reports which prerequisite is missing if either document is unsigned.

Who approves the generated technical documentation?▼

The Technical Lead holds final approval authority and must sign the document. The Solution Architect and DevOps Lead review content but do not gate the signature, while a Developer verifies the setup instructions work.

Why does the documentation generation fail validation?▼

Validation fails if prerequisites are unsigned, the document is not at its canonical path, placeholder text remains, sections are empty, the author field or TECH document ID is malformed, or cross-references point to missing documents. Each failure returns a specific error message.