Where are the documentation files stored?

The skill defaults to scanning 'docs/adr/' for records and places technical overviews in a date-stamped feature folder within the 'specs/' directory.

How does this skill help with system integration?

It specifically prompts for system boundaries and integration points, forcing a clear definition of how new components connect to existing infrastructure.

What is an ADR in the context of this skill?

An Architecture Decision Record (ADR) is a document that captures a significant architectural decision, including its context, the decision itself, alternatives considered, and the consequences of that choice.

Does this skill write the actual implementation code?

No, this skill is designed to focus on high-level planning and documentation, purposely excluding code snippets and line-by-line details to trust the implementer with the 'how'.

Architectural Tech Planner

Name: Architectural Tech Planner
Author: jkappers

byjkappers

Aprendizaje y Documentación

Generates comprehensive architectural plans and Architecture Decision Records (ADRs) to document system design and technology choices.

Acerca de

The writing-tech-plans skill provides a structured framework for architectural planning and decision-making within the Claude Code environment. It automates the creation of Architecture Decision Records (ADRs) and high-level technical overviews, guiding developers to consider system boundaries, data flow, and trade-offs before implementation begins. By focusing on systemic impact and long-term consequences rather than line-by-line code, this skill ensures that technical choices are well-reasoned, documented, and aligned with security best practices.

Características Principales

Structured data flow and integration mapping
Standardized ADR creation and automated numbering
System impact and component boundary analysis
0 GitHub stars
Comprehensive technical overview generation
Formalized trade-off and alternative evaluation

Casos de Uso

Evaluating and documenting significant technology choices or authentication approaches
Mapping the architectural impact of complex features before starting implementation
Maintaining a historical log of design decisions to align engineering teams

Acerca de

Características Principales

Structured data flow and integration mapping
Standardized ADR creation and automated numbering
System impact and component boundary analysis
0 GitHub stars
Comprehensive technical overview generation
Formalized trade-off and alternative evaluation

Casos de Uso

Evaluating and documenting significant technology choices or authentication approaches
Mapping the architectural impact of complex features before starting implementation
Maintaining a historical log of design decisions to align engineering teams