What is a TRD in the context of this skill?

A Technical Requirements Document (TRD) acts as an authoritative blueprint that guides the implementation and validation of a specific software feature or capability.

Why does the skill avoid terms like 'MVP' or 'Phase 2'?

It focuses strictly on 'what' the solution is rather than 'when' it will be built, ensuring the technical vision remains a timeless reference regardless of the release schedule.

How does the three-tier testing methodology work?

It categorizes tests into Level 1 (pure logic unit tests), Level 2 (real infrastructure integration), and Level 3 (full E2E workflows with real credentials).

Does it work with existing codebases?

Yes, it includes a context-reading protocol that scans project structure, ADRs, and existing capabilities to ensure new requirements align with the current architecture.

TRD Architect & Testing Blueprint

Name: TRD Architect & Testing Blueprint
Author: simonheimlicher

bysimonheimlicher

•

보안 및 테스팅

Generates authoritative technical requirements and three-tier testing strategies to guide rigorous feature implementation.

소개

The Writing TRD skill is a specialized framework for Claude Code that transforms project exploration into authoritative technical blueprints. It prioritizes a 'testing-first' methodology, ensuring that validation strategies, Behavior-Driven Development (BDD) scenarios, and infrastructure requirements are fully defined before implementation begins. By conducting deep-dive root cause analysis and enforcing a strict three-tier testing hierarchy (Unit, Integration, and E2E), this skill helps developers eliminate ambiguity and ensure that every technical requirement is measurable, feasible, and properly resourced.

주요 기능

Root cause and solution approach verification workflows
Three-tier testing methodology (Unit, Integration, E2E) mapping
1 GitHub stars
Automated BDD scenario generation for requirement validation
Infrastructure gap analysis for test harnesses and credentials
Strict scope boundary enforcement for timeless technical documentation

사용 사례

Drafting comprehensive technical specifications for new software features
Designing complex validation strategies for mission-critical systems
Auditing project infrastructure to identify testing blockers before development

소개

주요 기능

Root cause and solution approach verification workflows
Three-tier testing methodology (Unit, Integration, E2E) mapping
1 GitHub stars
Automated BDD scenario generation for requirement validation
Infrastructure gap analysis for test harnesses and credentials
Strict scope boundary enforcement for timeless technical documentation

사용 사례

Drafting comprehensive technical specifications for new software features
Designing complex validation strategies for mission-critical systems
Auditing project infrastructure to identify testing blockers before development