skills.rest
xiduzo
xiduzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

wtf.steer-tech

Generate a TECH.md with stack, architecture patterns, constraints, and ADRs.

7|2|Updated Apr 8, 2026
Search Tags:#architecture#documentation#adr#stack#tech-steering#technical-guidelines
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-steer-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wtf.steer-tech
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.steer-tech
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-steer-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate or refine a canonical tech guidelines document for the project.

Core Features & Use Cases

  • Generate and maintain a living TECH.md that captures the stack, architecture patterns, constraints, and ADRs.
  • Align engineering teams by providing a single source of truth for technical standards and decision records.
  • Use case: When a team needs to document or update their tech stack and architectural decisions to onboard new engineers.

Quick Start

Run the wtf.steer-tech skill to generate or update docs/steering/TECH.md using the tech-template and steering-doc-process.

Frequently Asked Questions about wtf.steer-tech

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

FAQPage Schema
How do I create a tech steering document for my software project?▼

To create a tech steering document, you need to define your stack, architecture patterns, constraints, and ADRs. The skill generates a canonical TECH.md file that serves as a single source of truth for technical standards and decision records.

What should be included in an architecture decision record (ADR) file?▼

An architecture decision record (ADR) file should include technical decisions regarding your stack, architecture patterns, and constraints. The generated TECH.md document captures these records to align engineering teams on specific architectural choices.

How do I document my tech stack and technical guidelines for team onboarding?▼

Documenting your tech stack and guidelines requires a living TECH.md file that captures architecture patterns, constraints, and ADRs. This provides a single source of truth for technical standards to successfully onboard new engineers.

What is the best way to maintain a living TECH.md for software architecture decisions?▼

The best way to maintain a living TECH.md is to refine it continuously using a structured steering doc process. This ensures your stack, architecture patterns, and constraints remain aligned with current engineering standards.

Can I refine an existing technical guidelines document without rewriting it from scratch?▼

Yes, you can refine an existing technical guidelines document by applying the steering doc process to your current TECH.md. This updates the stack, architecture patterns, and ADRs while maintaining the original structure.

Related Skills

Explore More Software Engineering Skills→
nahisahonahisaho
12

steering

Analyze codebases to generate steering documents and persistent project memory.

Community
Advanced
mwguerramwguerra
35

taskmanager

Convert PRD content into a hierarchical tasks.json task graph.

Community
Advanced
tobihagemanntobihagemann
399

commit-staged

Commit staged changes using predefined commit message conventions.

Community
Basic
rudironsonirudironsoni

dotnet-csharp-source-generators

Create and use Roslyn source generators in .NET with CSharpGeneratorDriver.

Community
Advanced