epicsagas

Git workspace manager — sync repos, bump versions, project health dashboard. Works in submodule monorepos, flat multi-repo, and single projects. Triggers: sync repos, pull all, bump version, git tags, overview, dashboard, project status.

Uses SkillOpt (text-space optimizer) to train and evolve natural-language skill documents for frozen LLM agents. Generates benchmark data from real tasks, builds environment adapters, runs rollout-reflect-aggregate-update training loops, and produces an optimized skill document. Triggers on: 'optimize skill', 'SkillOpt', 'skill training', 'improve this skill', 'skill experiment'.

Audits and guides OSS project release readiness across the full lifecycle: community standards, README quality, launch strategy, distribution pipeline, and governance/security posture. Activates when reviewing, planning, or shipping an open-source project — at any stage from initial setup to public launch.

Recommends and structures learning from a field completely outside the user's expertise. Generates a weekly reading plan with summary template for cross-pollination of ideas. Triggers on: 'learn something new', 'asymmetric learning', 'weekly learning', 'outside my field', 'cross-pollination'.

Business-first risk evaluation before writing code. Forces quantification of how a technical decision affects revenue, users, or market position within 30 days. Triggers on: 'biz risk', 'business value', 'is this worth it', 'prioritize', 'ROI'. No code without a business case.

Generates adversarial counter-arguments against the user's strongest technical convictions. Forces intellectual humility by constructing the best possible case against their position. Triggers on: 'devil's advocate', 'challenge my thinking', 'counter-argument', 'am I wrong', 'convince me otherwise'.

Tests that tools and products work outside the user's optimized development environment. Generates a compatibility checklist for lower-spec or general-purpose environments. Triggers on: 'env test', 'compatibility check', 'works on other machines', 'low spec test', 'production ready'.

Forces 5-level root-cause questioning on any technical decision or justification. Reveals whether the real motive is business value or technical satisfaction. Triggers on: 'five whys', 'why', 'root cause', 'justify this', 'why this approach'. No surface-level answers accepted.

Cold analysis of user's thinking patterns from conversation history — cognitive biases, logical blind spots, decision-making style, repetitive patterns. Triggers on: 'introspect', 'analyze my thinking', 'thinking patterns', 'my biases', 'self-analysis'. No praise — only evidence-based critique with actionable routines.

Forces minimum viable implementation check — can the project ship at 50% of current technical capability within 3 days? Strips scope to survival-level features. Triggers on: 'MVP', 'minimum viable', 'scope check', 'too big', '3-day rule', 'strip scope'.

Generates a plain-language project explanation for non-technical audiences and collects comprehension gaps. Identifies complexity that shouldn't exist in the product itself. Triggers on: 'explain simply', 'for non-tech', 'mom test', 'plain language', 'too complex to explain'.

Forces monthly external release of incomplete work. Generates a shipping checklist that prioritizes exposure over polish. Triggers on: 'ship it', 'release', 'not ready yet', 'almost done', 'need to perfect', 'monthly ship'.

Forces removal of 20% of active tools, plugins, and automation pipelines to prevent complexity stagnation. Identifies unused, redundant, or low-value system components. Triggers on: 'system diet', 'too many tools', 'declutter', 'simplify setup', 'tool audit'.

Scans codebase for technical debt markers (TODO, FIXME, HACK, XXX) and quantifies risk by severity, age, and blast radius. Generates a prioritized remediation plan. Triggers on: 'tech debt', 'TODO scan', 'debt audit', 'code hygiene', 'fixme', 'technical debt'.

Problem discovery for individuals, teams, and startups. Reframes vague ideas, solution-first thinking, and systemic complaints into structured problem definitions. Triggers on: 'discover', 'problem discovery', 'define the problem', 'what should we build', 'unclear requirements'.