Generate a Technical Design Document with file:line evidence from the codebase.
npx skills add https://github.com/cuozg/oh-my-unity --skill unity-document-tdd
Please help me install this Agent Skill. Skill: unity-document-tdd Source: https://github.com/cuozg/oh-my-unity/tree/main/skills/unity-document-tdd Command: npx skills add https://github.com/cuozg/oh-my-unity --skill unity-document-tdd
Produces rigorous, standardized Technical Design Documents that capture architecture decisions, implementation strategy, and dependency analysis to align teams and preserve rationale for future maintenance.
Provide the feature name and context, and the skill will generate a complete Technical Design Document using the template.
High-intent search queries and answers about installing and using this skill.
Generate a Technical Design Document by providing the feature name and context. The skill loads a TDD template and fills it with real project data to produce a complete document covering design, dependencies, and risks.
A Unity architecture design document should include Problem, Goals, Non-Goals, Design, Alternatives, Dependencies, Risks, and Open Questions sections. The generated TDD anchors decisions to the actual codebase to preserve maintenance rationale.
Write a technical design document grounded in codebase evidence by citing concrete file:line references for every claim. This grounds architecture decisions in real project data and justifies design choices with direct repository evidence.
Yes, TDD generation integrates with Unity standards to ensure architecture and quality practices are followed. This alignment ensures the generated design documents capture implementation strategy while adhering to established project conventions.
Yes, you can document architecture trade-offs and rejected alternatives before Unity implementation. The TDD explicitly captures multiple rejected options with rationale to inform future decisions and preserve the reasoning behind chosen designs.
samjhechtLocate similar code implementations and extract reusable patterns with file:line references.
ano4lDocument system architecture decisions with ADRs and diagrams in Mermaid, PlantUML, or ASCII.
tranvietanh0Implement Unity C# coding standards and naming conventions.
EnigmaWUWrite structured 12-field Architectural Decision Records using Kruchten's decision ontology.
