Loading...
Loading...
Found 8 Skills
Write clear, comprehensive technical documentation. Use when creating specs, architecture docs, runbooks, or API documentation. Handles technical specifications, system design docs, operational guides, and developer documentation with industry best practices.
Generate or sync a "Living Specification" (docs/spec.md) from source code to eliminate doc-code drift. Use when creating, updating, or reviewing architecture documentation for a directory or module. Triggers on requests like "generate spec", "create spec.md", "sync documentation", "update architecture docs", "/spec.doc", or when asked to document a codebase directory.
Write comprehensive technical documentation including user guides, how-to articles, system architecture docs, onboarding materials, and knowledge base articles. Creates clear, structured documentation for technical and non-technical audiences. Use when users need technical writing, documentation, tutorials, or knowledge base content.
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
Harness Engineering Phase 1 Step 2: Conduct in-depth analysis of project code and fill in the substantive content of each file in the docs/ knowledge base. Use this skill after the directory skeleton is created by harness-step1-create-agents-md. Immediately trigger this skill when the user says "fill document content", "improve docs/ files", "add substantive content to documents", "analyze project and write architecture document", "write ARCHITECTURE.md", or "write technical decision document". Prerequisite: The project already has AGENTS.md and the docs/ directory skeleton (created by harness-step1).
Push architecture docs to oh-my-mermaid cloud. Handles login, link, and push workflow with error guidance. Use when the user says "omm push", "push to cloud", "deploy architecture", or "share architecture".