Loading...
Loading...
Found 52 Skills
Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that propose technical changes, justifying design decisions in ADRs, constructing substantive code review feedback, or building a research argument or technical proposal.
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
Expert technical advisor with deep reasoning for architecture decisions, code analysis, and engineering guidance. Masters complex tradeoffs, system design, security architecture, performance optimization, and engineering best practices. Use when making critical architecture decisions, after implementing significant work, when debugging complex issues, encountering unfamiliar patterns, facing security/performance concerns, or evaluating multi-system tradeoffs. Provides comprehensive analysis with clear recommendations and rationale.
Create and manage Architecture Decision Records (ADRs). Use when documenting technology choices, design decisions, or architectural changes that need to be tracked over time. This is the CANONICAL ADR skill - all ADR-related work should use this skill.
Produces the technical design with architecture decisions, data flow, and a file change plan. Trigger: /sdd-design <change-name>, technical design, change architecture, how to implement.
Gather project context before drafting an ADR — business domain, system landscape, existing ADRs, related repos, LikeC4 model. Run BEFORE draft-adr when the architect is new to the system or context is thin. Back-and-forth Q&A with zero hallucination; every fact confirmed by the human before it counts.
Document the finalized tech stack selections, architecture decisions, long-term constraints, and coding conventions in the project into searchable permanent records. No one will remember why X was chosen six months later, but with decision documents, at least the background can be understood before making changes next time. Four categories: tech-stack (which tools/libraries/frameworks to use), architecture (how the system is organized), constraint (what is not allowed), convention (what is uniformly done). Trigger scenarios: Proactively trigger after making important choices during feature-design or issue-analyze, or when the user says "record the decision", "archive tech selection", "ADR", "record this constraint", "write down the convention". Only archive finalized decisions; do not archive proposed solutions under discussion.
Technical leadership advisor for CTOs on architecture decisions, engineering strategy, team scaling, technical debt management, and technology evaluation.
Create a new Architecture Decision Record in doc/adr/
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.
Creates agent-optimized technical design documents with context-layer-aware progressive disclosure for architecture decisions, component design, and data models. Use when writing technical designs, architecture docs, defining system components, or making technology choices for spec-driven development.