ilandahan/AID / skills/learning-mode
learning-mode
VerifiedDecision transparency, feedback collection, and debate invitations for AID methodology. Active in ALL phases for ALL roles.
| File | Kind | Size |
|---|---|---|
| QUICK-REFERENCE.extended.md | markdown | 5.0 KB |
| QUICK-REFERENCE.md | markdown | 2.2 KB |
| SIMULATION.extended.md | markdown | 19.2 KB |
| SIMULATION.md | markdown | 11.0 KB |
| SKILL.extended.md | markdown | 10.9 KB |
| SKILL.md | skill md | 4.5 KB |
| USER-FLOW.extended.md | markdown | 33.9 KB |
| USER-FLOW.md | markdown | 2.1 KB |
QUICK-REFERENCE.extended.md
View on GitHub# Learning Mode - Quick Reference
Fast lookup for Learning Mode triggers and formats.
---
## When to Use What
### π Decision Transparency
**USE WHEN:**
- β
Architecture decisions
- β
Technology choices
- β
Trade-off selections
- β
Scope decisions
- β
Pattern selection (with alternatives)
**SKIP WHEN:**
- β Obvious/simple choices
- β No alternatives exist
- β Standard patterns
### π¬ Debate Invitation
**USE WHEN:**
- β
Multiple viable options
- β
Trade-offs have no clear winner
- β
User preference vs best practice
- β
Scope is ambiguous
**SKIP WHEN:**
- β Single clear best answer
- β User already decided
- β Trivial decisions
### π Feedback Request
**USE WHEN:**
- β
Phase gate reached
- β
Major deliverable complete
- β
Uncertainty about direction
- β
Session ending
**SKIP WHEN:**
- β Minor task completion
- β Obvious next step
- β User just gave feedback
### π Learning Capture
**USE WHEN:**
- β
User provides correction
- β
User states preference
- β
Feedback indicates change needed
- β
User chooses unexpected option
---
## Block Formats
### Decision Transparency
```markdown
<decision-transparency>
**Decision:** [What]
**Reasoning:**
- [Factor]: [Impact]
**Alternatives Considered:**
1. [Alt] - Rejected: [why]
**Confidence:** [High/Medium/Low]
**Open to Debate:** [Yes/No]
</decision-transparency>
```
### Debate Invitation
```markdown
<debate-invitation>
**Topic:** [What we're deciding]
**Option A: [Name]**
- β
Pros: [list]
- β Cons: [list]
**Option B: [Name]**
- β
Pros: [list]
- β Cons: [list]
**My Lean:** [Which + why]
**But Consider:** [Counter-argument]
**Your Input Needed:** [Question]
</debate-invitation>
```
### Feedback Request
```markdown
<feedback-request>
**Context:** [What was done]
**Seeking Feedback On:**
1. [Aspect 1]
2. [Aspect 2]
**Questions:**
- [Specific question]
**Rating Request:** 1-5
**Improvement Ideas Welcome**
</feedback-request>
```
### Learning Capture
```markdown
<learning-captured>
**What I Learned:**
[Description]
**Source:**
- Context: [what]
- Date: [when]
**Applied To:**
- [How behavior changes]
**Verification:**
- [Next application]
</learning-captured>
```
---
## Phase-Specific Triggers
| Phase | Transparency | Debate | Feedback |
|-------|--------------|--------|----------|
| 1 PRD | Prioritization, Scope | Scope boundaries | Story completeness |
| 2 Tech Spec | Architecture, Tech stack | DB choice, Patterns | Spec readiness |
| 3 Breakdown | Task sizing, Dependencies | Granularity | Estimate accuracy |
| 4 Development | Pattern selection | Approach options | Code quality |
| 5 QA & Ship | Coverage decisions | Test strategy | Release readiness |
---
## Role-Specific Focus
| Role | Primary Transparency | Primary Debates | Primary Feedback |
|------|---------------------|-----------------|------------------|
| PM | Prioritization | Scope | Requirements |
| Dev | Pattern choices | Technical approach | Code quality |
| Lead | Architecture | Technology | Direction |
| QA | Coverage | Test strategy | Quality |
---
## Confidence Levels
| Level | When to Use | Action |
|-------|-------------|--------|
| **High** | Clear requirements, proven pattern | Execute |
| **Medium** | Some uncertainty, reasonable assumptions | Execute + note concern |
| **Low** | Multiple unknowns, risky assumptions | Invite debate or ask |
| **Uncertain** | Can't make informed decision | Ask clarifying question |
---
## Rating Scale (Feedback)
| Rating | Meaning | Response |
|--------|---------|----------|
| **5** | Excellent | Continue, capture what worked |
| **4** | Good | Minor tweaks, continue |
| **3** | Acceptable | Ask for improvement ideas |
| **2** | Needs work | Request specific changes |
| **1** | Off track | Full realignment needed |
---
## Anti-Patterns
| β Don't | β
Do Instead |
|----------|---------------|
| Debate trivial choices | Just decide and move on |
| Request feedback constantly | Only at milestones |
| Ignore user corrections | Capture as learning |
| Fake debates (obvious answer) | Use transparency |
| Over-explain simple things | Brief explanation only |
| Skip transparency on big decisions | Always show reasoning |
---
## Integration Checklist
Before completing significant work:
- [ ] Did I explain significant decisions?
- [ ] Did I invite debate where options exist?
- [ ] Did I request feedback at milestone?
- [ ] Did I capture user preferences as learnings?
- [ ] Did I avoid over-ceremony on simple tasks?
---
## Copy-Paste Templates
### Quick Decision Transparency
```markdown
<decision-transparency>
**Decision:**
**Reasoning:**
**Confidence:**
</decision-transparency>
```
### Quick Debate
```markdown
<debate-invitation>
**Topic:**
**Option A:** β
... β ...
**Option B:** β
... β ...
**My Lean:**
**Your Input:**
</debate-invitation>
```
### Quick Feedback
```markdown
<feedback-request>
**Context:**
**Rating Request:** 1-5
**Questions:**
</feedback-request>
```
### Quick Learning
```markdown
<learning-captured>
**Learned:**
**Applied:**
</learning-captured>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| 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: 194k | Updated | Claude CodeCodex | Verified | Install |