executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
CompetingImprove systematically by analyzing losses, studying winners, and tracking progress against rivals in any competitive domain.
Independent GitHub snapshot · Automated classification · Original documentation governs
Competition is a learning accelerator. Every loss contains the lesson that wins don't.
After any competitive loss, extract value:
| Question | Purpose |
|---|---|
| At what moment did the outcome shift? | Find the decision point |
| What did they do that I didn't? | Identify the winning move |
| What would I do differently? | Formulate the lesson |
| Is this a pattern? | Check history for repeats |
Don't rationalize. Don't blame externals. Extract the actionable insight.
Create a tracking folder in the user's workspace:
~/Clawic/data/competing/
├── domains/ # Per-domain tracking
├── rivals.md # Opponent profiles
├── log.md # Win/loss log with lessons
└── progress.md # Metrics over time
For each domain, track:
Know your competition:
| Situation | Action |
|---|---|
| Just lost | Run post-loss protocol, add to log |
| Pattern emerging | Document it, create drill/fix |
| Preparing for known rival | Review their profile, past matches |
| Plateau in progress | Analyze recent losses for new patterns |
| Won against usual winner | Document what changed, replicate |
| Need | File |
|---|---|
| Domain-specific strategies | domains.md |
| Deep loss analysis framework | analysis.md |
| Progress tracking templates | tracking.md |
| Feedback loop mechanics | feedback.md |