Skill
Technical Documentation
Turn an approved design into production-ready technical docs an AI agent can build from.
// workflow;Behaviour
What it does
- Expands a design spec into architecture, data model, API contracts, and more
- Proposes a doc subset scaled to the project, not every doc for every tool
- Tags every technical decision as human-locked, agent-discretion, or needs-decision
- Drafts AI-owned sections while surfacing choices for human review
- Writes living docs to docs/technical/ with no dates in filenames
- Hands off to planning on greenfield work, or conformance-check on brownfield
When to use
Good fits
After brainstorming, when the what and why are clear
Starting a new project or feature that needs architecture written down
Before planning, when the agent needs locked stack and constraint context
When you want reviewable docs instead of jumping straight to code
Development harness
Step 2 of 8 · Design
Part of the design-to-ship pipeline: brainstorming → technical-documentation → conformance-check → reconciling-changes → planning → project-setup → executing-plans → shipping. Install the full set for structured feature work.
Install
Get this skill
Uses Agent Kit via npx; no global install required.
Quick install
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill technical-documentationGlobal (Cursor)
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill technical-documentation --global --agent cursorGlobal (Claude)
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill technical-documentation --global --agent claudeProject install
npx @levi-putna/agent-kit@latest add levi-putna/skills --skill technical-documentation --projectInteractive install
npx @levi-putna/agent-kit@latest add levi-putna/skillsUninstall
npx @levi-putna/agent-kit@latest remove technical-documentationExample
Example prompt
The design spec is approved. Write the technical docs for this checkout flow.
Flow
How the skill works
- Read the approved design spec and scan for existing material
- Propose which docs to write for this project type
- Draft each document with explicit decision ownership tags
- Surface open decisions and resolve them with the user
- Save to docs/technical/ and hand off to planning or conformance-check