swa-retro

Guide software architect retrospectives to review technical decisions and architectural patterns.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hilaryosborne/skills --skill swa-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swa-retro
Source: https://github.com/hilaryosborne/skills/tree/main/software-architect/swa-retro
Command: npx skills add https://github.com/hilaryosborne/skills --skill swa-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps facilitate and structure retrospectives specifically for software architects, ensuring a focused and productive review of technical design and implementation decisions.

Core Features & Use Cases

  • Structured Retrospective Guidance: Provides a framework for conducting software architect retrospectives.
  • Focus on Technical Decisions: Helps identify learnings and improvements related to architectural choices, patterns, and non-functional requirements.
  • Use Case: After a major feature release, the software architect uses this skill to guide a retrospective discussion on the chosen architectural patterns and their impact on performance and maintainability.

Quick Start

Initiate a software architect retrospective using the swa-retro skill.

Frequently Asked Questions about swa-retro

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

FAQPage Schema
How do I conduct a software architecture retrospective for my team?▼

To conduct a software architecture retrospective, use a structured framework to review technical decisions and architectural patterns. This helps identify improvements in system design and non-functional requirements after a major project or feature release.

What should a technical review retrospective focus on?▼

A technical review retrospective should focus on evaluating technical decisions, architectural patterns, and non-functional requirements. It targets system design improvements and overall technical strategy to ensure continuous improvement in software architecture.

When do I need to run a retrospective for system design?▼

You need to run a retrospective for system design after major feature releases or project milestones. It provides structured guidance for post-project analysis to evaluate architectural choices and their impacts on performance.

Can I use this to review non-functional requirements after a release?▼

Yes, you can review non-functional requirements after a release. The retrospective framework specifically helps software architects identify learnings and improvements related to architectural choices and non-functional requirements.

Does this framework require structured prompts for post-project analysis?▼

Yes, this retrospective framework requires structured prompts and guidance. These structured inputs are necessary to facilitate an effective post-project analysis and ensure a focused review of technical design decisions.

What is the best way to improve technical strategy through continuous improvement?▼

The best way to improve technical strategy through continuous improvement is by facilitating structured software architecture retrospectives. This process focuses on identifying actionable improvements in system design and architectural patterns.