Loading...
Loading...
Found 7 Skills
Self-evolving context protocol that captures insights, prevents repeated mistakes, and evolves project documentation through structured feedback loops.
Use when a codebase, product, workflow, runtime, or organization needs purpose-first whole-machine stewardship: understand what the whole system is trying to produce, then improve the machinery, tooling, feedback loops, operability, and developer flow that let it produce that output.
Apply systems thinking — causal loop diagrams, stock-and-flow models, system archetypes, and leverage-point analysis — to organizational, economic, or social problems where feedback loops, delays, or emergent behavior drive recurring failure across multiple interacting actors. Use this skill when the user describes a multi-actor situation that resists linear fixes: policy interventions that backfire, org-level fixes that break other teams, market symptoms that return after being solved, or time-lagged second-order consequences, even if they say 'why does fixing X make Y worse' or 'identify the leverage points in this system'. Do NOT use for single-cause software bugs, flaky tests, or regressions — those are debugging problems, not systems-thinking problems, even when phrased as 'this keeps coming back'.
When behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.
Use this skill when building community programs, moderating forums, creating advocacy programs, or managing feedback loops. Triggers on community management, forum moderation, advocacy programs, community engagement, feedback loops, community metrics, and any task requiring community strategy or operations.
Apply George Mack's High Agency approach to founder and leadership execution. Use when facing ambiguity, blockers, stalled execution, "impossible" constraints, cross-functional deadlock, or high-uncertainty decisions that require ownership and rapid action.
Analyze complex systems from elements to relationships, from parts to the whole, and from static to dynamic perspectives. Suitable for scenarios where problems recur, where a single change affects the entire system, and where treating symptoms doesn't work. When you find that 'the harder you work, the worse it gets' or 'problems keep recurring', you need to switch to systematic thinking to find root solutions. Not applicable to simple single-cause problems or emergency scenarios requiring quick action. Key trigger signals: 'Why does this problem keep recurring?', 'Fixing A broke B instead', 'Feeling stuck in a loop'.