feedback-loop

Automate collection of learnings, ADRs, and retrospective insights via /feedback commands.

1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/tygwan/AgenticREVIT --skill feedback-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feedback-loop
Source: https://github.com/tygwan/AgenticREVIT/tree/main/.claude/skills/feedback-loop
Command: npx skills add https://github.com/tygwan/AgenticREVIT --skill feedback-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the collection of learnings, architectural decisions, and retrospective insights, ensuring institutional knowledge is captured and accessible.

Core Features & Use Cases

  • Learning Capture: Record insights from issues, resolutions, and patterns.
  • ADR Management: Generate and organize Architecture Decision Records.
  • Retro Prompts: Create retrospective prompts to guide team improvements.

Quick Start

Use the /feedback command to start capturing learnings, ADRs, and retrospectives for your project. For example, /feedback learning "Resolved a recurring bug by applying a pattern" and /feedback adr --title "Caching Strategy" --status proposed.

Frequently Asked Questions about feedback-loop

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

FAQPage Schema
How do I capture learnings and architectural decisions from my software projects?

Capture learnings and architectural decisions using the /feedback command to automate collection of insights from issues, resolutions, and design changes. The Skill records these as structured learnings and Architecture Decision Records (ADRs) accessible to your team.

What's the difference between recording a learning and generating an ADR?

Learnings document insights and patterns from issues and resolutions, while ADRs formally capture architectural decisions with status and rationale. Both are automated via /feedback commands—learnings focus on retrospective insights, ADRs on design choices and their justification.

Can I use this to run retrospectives and capture team feedback?

Yes. The Skill generates retrospective prompts and templates via /feedback retro commands to guide team discussions, ensuring improvements and insights are systematically captured and stored for future reference.

How do I organize ADRs and learnings for my engineering team?

The Skill automates ADR and learning collection, organizing them as institutional knowledge accessible across your team. Use /feedback commands to generate, title, and tag records so they're discoverable and tied to specific deployments or design changes.

Do I need special setup or dependencies to start capturing feedback?

No dependencies are required. Start immediately using /feedback commands to record learnings, ADRs, and retrospective prompts. The Skill works with any software project and engineering team structure.

What happens to feedback and ADRs after I capture them?

Captured learnings, ADRs, and retrospective insights are stored as accessible institutional knowledge. This prevents knowledge loss, enables pattern recognition across issues and deployments, and informs future architectural and operational decisions.