learning-mode

Document decision reasoning, alternatives, feedback, and captured learnings.

9|2|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/ilandahan/AID --skill learning-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learning-mode
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/learning-mode
Command: npx skills add https://github.com/ilandahan/AID --skill learning-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables auditable, transparent decision-making by surfacing reasoning, inviting debate, collecting feedback, and capturing learnings to improve future recommendations across all project phases and roles.

Core Features & Use Cases

  • Decision Transparency: Show the factors that influenced major decisions, including alternatives considered and confidence levels.
  • Feedback Integration: Automatically request and incorporate feedback at phase gates and milestones.
  • Debate Invitation: Propose multiple viable options when trade-offs exist and invite user input.
  • Learning Capture: Record corrections and learnings to refine future guidance.

Use Case: In a Phase 2 Tech Spec meeting, generate a decision transparency block for architecture choices, then open a debate on the chosen approach and capture the final learnings.

Quick Start

Start by prompting Learning Mode to create a decision-transparency block for a significant decision, then ask for feedback and optionally a debate invitation, and finally capture any learning from the session.

Frequently Asked Questions about learning-mode

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

FAQPage Schema
How do I document architecture decisions and alternatives considered for technical trade-offs?

To document architecture decisions with auditable transparency, you generate a decision-transparency block that explicitly records alternatives considered, trade-offs, and confidence levels. This process ensures technical choices are fully traceable for future review.

What is the best way to collect feedback at project phase gates?

Collecting feedback at phase gates requires automatically requesting and incorporating stakeholder input at project milestones. This approach captures phase-gate feedback directly into the decision pipeline, ensuring team alignment before moving forward.

How do I invite debate on multiple viable technology choices during a spec review?

To invite debate on technology choices during a spec review, you propose multiple viable options when trade-offs exist and actively request user input. This debate invitation surfaces diverse perspectives before finalizing the architecture.

Can I capture learnings from spec meetings to improve future recommendations?

You can capture learnings from spec meetings by recording corrections and session outcomes to refine future guidance. Learning capture ensures that past decisions and feedback directly improve the system's subsequent recommendations.

Does decision transparency work for all roles across different project phases?

Decision transparency applies to all roles and across all project phases, from initial architecture choices to final phase-gate reviews. It satisfies the universal need for clear alternatives documentation and feedback integration regardless of discipline.