create-technical-design-doc
Assimilated TLC TDD writer. Create architecture-level Technical Design Documents through discovery. Triggers: write a design doc, create a TDD, technical spec, architecture document, RFC, design proposal, criar um TDD. Do not use for README, API docs, or general docs (docs-writer).
- License 许可
- CC-BY-4.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- create-technical-design-doc
- license
- CC-BY-4.0
- metadata
- { "author": "Tech Leads Club", "version": "1.0.0", "owner_agent": "codenavi-agent" }
- description
- Assimilated TLC TDD writer. Create architecture-level Technical Design Documents through discovery. Triggers: write a design doc, create a TDD, technical spec, architecture document, RFC, design proposal, criar um TDD. Do not use for README, API docs, or general docs (docs-writer).
02 资源文件 10
- 参考文档.skill-meta.json120 B
- 参考文档PERMISSIONS.yaml332 B
- 参考文档POLICY.md149 B
- 参考文档references/lenses/retained/legacy-contract.md230 B
- 参考文档references/ORIGINAL_SKILL.md50.8 KB
- 参考文档references/package-notes.md156 B
- 参考文档references/provenance.md987 B
- 参考文档references/tlc/README.md10.3 KB
- 参考文档references/tlc/UPSTREAM.md50.8 KB
- 参考文档references/usage-and-verification.md1.2 KB
03 SKILL.md 正文
Technical Design Doc Creator
Governance: CodENavi Full Workspace v2. Skill of codenavi-agent; inherit AGENTS.md.
Lifecycle: BRIEFING → RECON → PLAN → EXECUTE → VERIFY → DEBRIEF.
Source roles/workers are internal lenses. Never create agent identities or bypass runtime secret/permission gates.
Assimilated from installed technical-design-doc-creator. Original contract: references/ORIGINAL_SKILL.md.
Identity
A skill of the single canonical codenavi-agent. It creates no new agent identity.
Mission
Write a TDD that records architectural decisions and contracts, not implementation code. Match the user's language. Size sections to project scale.
Activation
- User asks for a TDD, design doc, RFC, tech spec, or architecture document before implementation.
Non-activation
- README, API reference, or general documentation (
docs-writer). - Feature execution (
spec-driven/spec-driven-lean).
Critical rules
- Mandatory sections: header, context, problem, scope, technical solution, risks, implementation plan.
- Security is mandatory for payments/auth/PII. Monitoring and rollback are mandatory for production.
- Document decisions that survive a framework change. No CLI recipes or framework-specific code as the design.
- Do not invent missing facts. Ask only for forks that change the outcome; otherwise state the assumption.
- Follow templates and checklists in
references/ORIGINAL_SKILL.md.
Continuity
A TDD does not replace AEOS specs preflight when implementation will mutate the repo.
TLC source
For the catalog workflow and its local resources, read TLC contract. Apply root governance and the local constraints above; upstream does not grant extra authority.
Provenance and source freshness: provenance.
Example usage and failure handling: read usage and verification when selecting this skill or a required step fails. Read package-notes.md only when the domain workflow needs that supporting context; root governance and this entry take precedence.
04 同仓库更多 Skills
workspace-brain
Operate the CodENavi workspace brain MCP and CLI — cloud DeepSeek RAG, disk corpus at WORKSPACE_BRAIN_ROOT, Jev URL curation, and event logging for Cursor/Codex/OpenCode/Claude. Use when ingesting repo knowledge, asking the brain, mapping web seeds, or recording AI-driven file changes. Do NOT use for local Ollama RAG or storing API keys in git.
workbench-profile-resolver
Provide enterprise-grade capability for `workbench-profile-resolver` inside AEOS v1.1. Use when the user requests workbench profile resolver or invokes workbench-profile-resolver. Do NOT use for unrelated tools or unapproved remote writes.
wordpress-expert
Staff-level WordPress engineering super-skill for one-shot site mapping, clean-code AI-assisted project creation/modification, the complete installed plugin universe, governed remote wp-admin operations, themes/blocks/layout, third-party integrations and production-safe changes. Use when the user requests wordpress expert or invokes wordpress-expert. Do NOT use for unrelated languages, domains or production deployment.
whatsapp-simulator
Generate synthetic WhatsApp-style conversation fixtures for testing conversational systems, support flows and automation. Use when the user requests whatsapp simulator or invokes whatsapp-simulator. Do NOT use for unrelated tools or unapproved remote writes.
web-quality-audit
Assimilated TLC/web-quality multi-area audit. Review performance, accessibility, SEO and best practices in one pass. Triggers: audit my site, review web quality, check page quality, optimize my website across areas. Do not use for a single-area job (core-web-vitals, ai-seo, best-practices, perf-lighthouse).
voiceai
Provide an evidence-backed voice interface for AEOS. Activating this skill is treated as explicit current-session consent for `voiceai` to record user audio or transcribe audio from user-authorized audio/video media within the declared scope. The skill can: Use when the user requests voiceai or invokes voiceai. Do NOT use for unrelated tools or unapproved remote writes.