Maintains project-specific known-issues.md mapping recurring errors to solutions. Auto-consulted by systematic-debugging before investigations; triggers on 'save this fix', 'remember this error', or known issues phrases.
npx claudepluginhub repozy/superpowers-optimizedThis skill uses the workspace's default tool permissions.
Maintain a project-level error→solution mapping to avoid rediscovering known problems.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Maintain a project-level error→solution mapping to avoid rediscovering known problems.
known-issues.md at the project root (same level as package.json, Cargo.toml, etc.).
Before starting any debugging investigation:
known-issues.md exists.After resolving a bug that is likely to recur:
Do NOT record:
Each entry must be concise and actionable:
## [Short description]
**Error:** `exact error message or pattern`
**Cause:** One sentence explaining why this happens.
**Fix:**
```bash
exact command or steps to resolve
Context: When this typically occurs (e.g., "after fresh clone", "on Windows", "when DB is not running").
## File Management
- Keep `known-issues.md` under 50 entries. If it grows beyond that, prune entries that haven't been relevant in months.
- Group entries by category (Environment, Dependencies, Tests, Build, Platform).
- When a known issue is permanently fixed (e.g., the root cause was removed from the codebase), delete the entry.
## Integration
- `systematic-debugging` consults this file in Phase 1 (Investigate) before generating hypotheses.
- `using-superpowers` reads this file during the entry sequence when it exists.
- After resolving a debugging session, offer to add the error→solution mapping if it meets the "When to Update" criteria.