tech-specification

Identify repository technology stacks and delegate analysis to specialized docbook sub-skills.

5|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/d4rkNinja/code-guardian --skill tech-specification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-specification
Source: https://github.com/d4rkNinja/code-guardian/tree/main/docs-workspace/skills
Command: npx skills add https://github.com/d4rkNinja/code-guardian --skill tech-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of comprehensive technical specifications by identifying project technology stacks and routing deep analysis to specialized sub-skills, saving time for engineering teams.

Core Features & Use Cases

  • Automated tech-stack identification: Detects languages and frameworks present in the repository and selects the appropriate sub-skill.
  • Delegation to sub-skills: Offloads in-depth documentation to targeted docbooks (node_docbook.md, python_docbook.md, go_docbook.md, java_docbook.md, etc.).
  • Use Case: When starting a new project, generate a high-level spec and an implementation plan with recommended tooling and patterns.

Quick Start

Use the tech-specification skill to trigger a stack-detection workflow and obtain a structured technical specification for a repository.

Frequently Asked Questions about tech-specification

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

FAQPage Schema
How do I automate tech spec generation for a repository?▼

To automate tech spec generation, the skill identifies the repository project technology stack and delegates deep architectural analysis to specialized sub-skills, producing structured technical specifications automatically.

What is the best way to document a software project architecture automatically?▼

The best way to document architecture automatically is by detecting repository languages and frameworks, then delegating in-depth architectural analysis to specialized docbooks to produce comprehensive technical specifications.

Do I need a SKILL.md file at the repo root to generate technical specifications?▼

Yes, generating technical specifications requires a valid SKILL.md file at the repository root, which the workflow relies on along with the docbook reference guide to determine the correct sub-skill for documentation.

Can I use this tech-spec workflow for any programming language?▼

Yes, the tech-spec workflow applies to software projects at any language or runtime, triggering respective docbook sub-skills like node_docbook, python_docbook, go_docbook, or java_docbook based on repository findings.

How does the tech specification process handle multiple frameworks in one repository?▼

The tech specification process handles multiple frameworks by identifying the project technology stack and selecting the appropriate sub-skill, routing deep architectural analysis to the matching specialized docbook for accurate documentation.

What limitations exist when delegating repository analysis to sub-skills?▼

A key limitation is the strict dependency on a valid SKILL.md at the repository root and the docbook reference guide; without these, the workflow cannot determine the correct sub-skill to route the architectural analysis.