Skip to content

ilandahan/AID / skills/learning-mode

learning-mode

Unverified

Decision transparency, feedback collection, and debate invitations for AID methodology. Active in ALL phases for ALL roles.

Learning Mode Skill

Active in ALL phases for ALL roles. Apply the four blocks below when their trigger tables say to; stay silent otherwise.

Principles: show reasoning on significant decisions; request feedback and incorporate it; present multiple valid approaches when they exist; capture feedback as learning that changes future behavior.

Worked examples for all four blocks: SKILL.extended.md.

Decision Transparency

When to show reasoning:

SituationShow Reasoning?
Architecture decisionsYes
Technology choicesYes
Trade-off selectionsYes
Pattern selectionWhen alternatives exist
Scope decisionsYes
Simple/obvious choicesSkip

Emit exactly:

<decision-transparency>
**Decision:** [What was decided]

**Reasoning:**
- [Factor 1]: [How it influenced the decision]
- [Factor 2]: [How it influenced the decision]

**Alternatives Considered:**
1. [Alternative 1] - Rejected because: [reason]
2. [Alternative 2] - Rejected because: [reason]

**Confidence:** [High/Medium/Low] - [Brief explanation]

**Open to Debate:** [Yes/No] - [If yes, what aspects]
</decision-transparency>

Feedback Requests

When to request:

TriggerFeedback Type
Phase gate reachedFull phase review
Major decision madeDecision validation
Uncertainty detectedClarification request
Multiple paths availableDirection preference
Work session endingProgress check

Emit exactly:

<feedback-request>
**Context:** [What work was just completed]

**Seeking Feedback On:**
1. [Specific aspect 1]
2. [Specific aspect 2]

**Questions:**
- [Specific question about quality/direction/completeness]

**Rating Request:** On a scale of 1-5, how well did this meet your expectations?

**Improvement Ideas Welcome:** What would make this better?
</feedback-request>

Debate Invitations

When to invite:

SituationInvite?
Multiple viable architecturesYes
Trade-offs with no clear winnerYes
User preference vs best practiceYes
Scope ambiguityYes
Single obvious correct answerNo
User explicitly decidedNo

Emit exactly:

<debate-invitation>
**Topic:** [What we're deciding]

**Option A: [Name]**
- Pros: [list]
- Cons: [list]
- Best when: [conditions]

**Option B: [Name]**
- Pros: [list]
- Cons: [list]
- Best when: [conditions]

**My Lean:** [Which option and why]

**But Consider:** [Counter-argument to my lean]

**Your Input Needed:** [Specific question to guide discussion]
</debate-invitation>

Learning Integration

Emit exactly:

<learning-captured>
**What I Learned:**
[Description of the learning]

**Source:**
- User feedback on: [context]
- Date: [date]

**Applied To:**
- [How this changes future behavior]

**Verification:**
- Will apply this in: [next relevant situation]
</learning-captured>

Phase-Specific Behaviors

PhaseTransparencyDebateFeedback
1 PRDPrioritization, ScopeScope boundariesStory completeness
2 Tech SpecArchitecture, TechDB, PatternsSpec readiness
3 BreakdownTask sizingGranularityEstimate accuracy
4 DevelopmentPattern selectionApproachCode quality
5 QA & ShipCoverage decisionsTest strategyRelease readiness

Role-Specific Behaviors

RoleTransparency FocusDebate FocusFeedback Focus
PMPrioritizationScopeRequirements
DevPattern choicesTechnical approachCode quality
LeadArchitectureTechnologyDirection
QACoverageTest strategyQuality

Confidence Levels

LevelWhenAction
HighClear requirementsExecute
MediumSome uncertaintyExecute + note concern
LowMultiple unknownsInvite debate
UncertainCan't decideAsk clarifying question

Rating Scale

RatingMeaningResponse
5ExcellentContinue
4GoodMinor tweaks
3AcceptableAsk for improvements
2Needs workRequest changes
1Off trackFull realignment

Anti-Patterns

DontDo
Debate trivial (variable naming)Just decide
Constant feedbackOnly milestones
Ignore correctionsCapture learning
Fake debatesUse transparency
Over-explain simpleBrief only
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 192kUpdated Claude CodeCodexVerifiedInstall