critical-perspective
Engage in critical thinking by questioning assumptions, exploring alternative perspectives, and uncovering latent topics in conversations. Use when discussions could benefit from deeper exploration, when identifying blind spots, or when broadening understanding through respectful challenge and curiosity-driven inquiry.
cognitive-variability
Guide conversations through dynamic shifts between zoom levels (scale) and connecting/exploring (intent) to unlock creative breakthroughs and prevent rigid thinking. Use when the user is stuck or needs to develop an idea or when there is a sense of too much repetition or dispersion. Takes the user through several stages of thinking — from idea genesis, to development, to questioning, to disruptive thinking. Identifies structural gaps between idea clusters as spaces for innovation. Tracks temporal dwelling patterns and manages cognitive energy expended. Uses playfulness for difficult transitions from chaos to clarity. Maximum creative potential lives in gaps and dissipative states. Apply for complex analysis, brainstorming, being stuck, breakthroughs, decision paralysis, group facilitation, breaking repetitive patterns, or when grammatical patterns reveal cognitive issues.
brainstorming
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
model-mediated-development
Use when building any system that involves AI/model calls - integrates with brainstorming, planning, and TDD to ensure model agency over hardcoded rules
systematic-debugging
This skill should be used when debugging complex kernel issues requiring systematic investigation and documentation. Use for documenting problem analysis, root cause investigation, solution implementation, and evidence collection following Breenix's Problem→Root Cause→Solution→Evidence pattern.
exploration
Technical exploration within existing projects. USE WHEN user says "think through", "explore options", "investigate", "how should we approach", or needs to evaluate approaches before implementation. Creates exploration documents in project's explorations/ folder. Not for new project ideas—use ideation skill for that.
diagram
Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.
brainstorming
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation.
wise-novice
Approach problems with beginner's mind while asking penetrating questions. Use when seeking fresh perspectives, cutting through complexity, challenging expert assumptions, simplifying explanations, or when deep domain knowledge may be creating blind spots.
model-first-reasoning
Apply Model-First Reasoning (MFR) to code generation tasks. Use when the user requests "model-first", "MFR", "formal modeling before coding", "model then implement", or when tasks involve complex logic, state machines, constraint systems, or any implementation requiring formal correctness guarantees. Enforces strict separation between modeling and implementation phases.
stress-testing
Stress-test plans, proposals, and strategies. Use for pre-mortems, assumption audits, risk registers, evaluating business ideas, identifying failure modes, or when you need devil's advocate analysis before committing resources.
dreaming
Think expansively and imaginatively without practical constraints. Use when brainstorming ambitious ideas, exploring what's possible, challenging assumptions, envisioning ideal futures, or when the user needs to break out of incremental thinking and imagine boldly.
10x-vision
Strategic amplification mode that reveals blind spots, untapped opportunities, and hidden leverage points in any business strategy, entrepreneurship idea, or creative content project. Cuts through noise to show what others miss.
code-analysis
Provides methodologies, metrics, and best practices for analyzing code structure, complexity, and quality
autonomous-development
Comprehensive autonomous development strategies including milestone planning, incremental implementation, auto-debugging, and continuous quality assurance for full development lifecycle management
Decision Frameworks
Decision-making methodologies, scoring frameworks, and planning strategies for Group 2 agents in four-tier architecture
tdd-methodology-expert
Use proactively when you need to implement features or fix bugs using strict Test-Driven Development (TDD) methodology. This agent should be activated for any coding task that requires writing new functionality, refactoring existing code, or ensuring comprehensive test coverage, but should not be used for any design-related tasks. The agent excels at breaking down complex requirements into testable increments and maintaining high code quality through disciplined TDD cycles. Use this agent proactively or if the user mentions 'TDD', 'tdd' or 'Test Driven Development'.
environmental-scanning-foresight
Use when scanning external trends for strategic planning, monitoring PESTLE forces (Political, Economic, Social, Technological, Legal, Environmental), detecting weak signals (early indicators of change), planning scenarios for multiple futures, setting signposts and indicators for early warning, or when user mentions environmental scanning, horizon scanning, trend analysis, scenario planning, strategic foresight, futures thinking, or emerging issues monitoring.
Page 8 of 16 · 272 results