athola
athola / action-first-output
338Shapes turns action-first: action leads, steps numbered, state restated. Use for ADHD-friendly output. Do not use to trim tokens; use response-compression.
athola / blast-radius
338Analyzes code change impact with risk scoring and affected-node mapping. Use before merging to understand what a change touches and what lacks test coverage.
athola / cpu-gpu-performance
338Establishes CPU/GPU baselines before resource-intensive operations. Use before builds, training runs, or any task that pins cores or GPUs for over a minute.
athola / decisive-action
338Guides when to ask clarifying questions versus proceed autonomously. Use to reduce unnecessary clarifying questions when intent is clear.
athola / delegation-core
338Delegates execution to eight CLIs (Gemini, Qwen, MiniMax, GLM, Muse, Codex, OpenCode, Glimmer). Use for execution tasks. Do not use for secrets.
athola / dorodango
338Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
athola / git-workspace-review
338Verifies workspace state and staged changes as a read-only preflight. Use before commits or PRs to confirm staged set is clean and correct.
athola / night-market-collective-memory
338Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.
athola / night-market-completion-integrity-campaign
338Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.
athola / project-brainstorming
338Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.
athola / project-execution
338Executes implementation plans with progress tracking, checkpoint validation, and quality gates. Use after planning is complete and tasks are ready to implement.
athola / project-planning
338Converts a specification into a phased, dependency-ordered implementation plan. Use after specification is complete and before execution begins.
athola / project-specification
338Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
athola / proof-of-work
338Enforces validation and evidence before claiming work complete. Use before declaring implementation done, creating a PR, or submitting deliverables for review.
athola / provider-setup
338Reports which delegation CLIs are installed and authenticated, installs missing ones, and stores the result. Use before delegating or when a provider errors.
athola / release-health-gates
338Standardizes release approvals with GitHub-aware checklists and deployment gates. Use before releasing to production to verify all gates pass.
athola / review-chamber
338Captures and retrieves PR-review findings in memory palaces. Use after PR review to store architectural decisions, patterns, and standards for future reference.
athola / review-core
338Provides review-workflow scaffolding for context, evidence, and output. Use at the start of any detailed review to ensure consistent, comparable findings.
athola / stack-push
338Pushes all branches in a stack and opens or updates one dependent PR per slice. Use after stack-create to publish the stack or after adding commits to a slice.
athola / token-conservation
338Enforces token quota management at session start with conservation and compression checks. Use at the start of every session or before large context loads.