doc-architect

Reverse-engineer codebases into platform-agnostic Functional, Technical, and Test documentation.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/NikhilVijayakumar/Yantra --skill doc-architect-nikhilvijayakumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-architect
Source: https://github.com/NikhilVijayakumar/Yantra/tree/main/.agent/skills/doc-architect
Command: npx skills add https://github.com/NikhilVijayakumar/Yantra --skill doc-architect-nikhilvijayakumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates consistent, platform-agnostic documentation blueprints (Functional, Technical, and Test) that guide the lifecycle of software modules and enable rapid handover across teams.

Core Features & Use Cases

  • Trinity documentation: generate Functional, Technical, and Test plans for each module.
  • Architecture-friendly scaffolding: provide README-level docs and test templates that remain language-agnostic.
  • Documentation-driven governance: align development with standardized documentation structure and auditing workflows.

Quick Start

Document [Module] to generate the Trinity docs scaffolds for a module and align tests with a standardized structure.

Frequently Asked Questions about doc-architect

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

FAQPage Schema
How do I generate architecture documentation from an existing codebase?

You can generate architecture documentation by reverse-engineering a modular codebase into platform-agnostic blueprints, producing Functional, Technical, and Test plans for each module under docs/features/{module}.

What is Trinity-style documentation for software modules?

Trinity-style documentation is a standardized structure that creates Functional, Technical, and Test plans for each software module to guide its lifecycle and enable rapid team handover.

Can I use platform-agnostic blueprints for any programming language?

Yes, platform-agnostic blueprints are language-agnostic and apply to any modular software project, generating README-level docs and test templates without being tied to a specific framework.

What's the best way to align unit and E2E tests with module documentation?

The best way to align tests with documentation is scaffolding unit and E2E test templates alongside Trinity blueprints, ensuring standardized ID mappings between tests and module docs.

How does documentation-driven governance handle code drift during audits?

Documentation-driven governance flags drift against code for audit readiness by maintaining standardized documentation structure and ensuring generated blueprints remain aligned with the actual codebase.