work-item-routing
Route work items to correct tables (feedback, features, build_tasks)
in-the-details-review-loop
A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) weekly rather than just metrics or status slides. Use when feeling product quality is slipping or team is moving too slowly.
generate-reskin-checklist
Generate a checklist for the legacy reskin given a specific criteria
refactoringtechniques
Refactoring Techniques refactoring skill
explorer-vs-lecturer-coaching-model
A feedback approach where the manager acts as a curious investigator rather than an authoritarian expert, using observation and questions to help direct reports self-diagnose issues. Use during 1:1s and performance reviews.
task-classification
Classifies tasks by complexity pattern for smart routing. Auto-invoked for all implementation requests.
estimate-stories
Calculate story point estimates for user stories using structured formula (Complexity × Effort + Risk). Analyzes acceptance criteria, assesses complexity (1-5), effort (1-5), and risk (0-3), then documents estimation rationale. Use during backlog grooming or sprint planning when stories need sizing.
dev-guided
Human-in-the-loop iterative development. Use when requirements will emerge during implementation, decisions need human approval at each step, or work will span multiple sessions with frequent feedback loops. Creates problem statement, decisions log, runbook, and progress tracking.
jiraprepare
Prepare a Jira task with enrichment and subtask creation. Use when the user wants to "prepare task", "enrich issue", "create subtasks", or "prepare for development".
lno-time-management-framework
Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (<1x) to escape the trap of treating all tasks as equally important. Apply perfectionism only to L tasks.
plan-on-md
A skill to save plans to local Markdown after creating them in plan mode
pre-mortem-framework
Instead of waiting for a post-mortem after failure, imagine the project has already failed spectacularly and work backward to uncover hidden risks. Use before kicking off any major initiative, product launch, or high-stakes project.
phase-planning
Generate 5-phase implementation plan with validation gates and resource allocation. Adapts phase count and timeline based on complexity score. Includes validation gates between phases. Use when: planning implementation, need structured timeline, want validation checkpoints.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
improve-tbta
Systematically work through TBTA features using the 6-stage STAGES.md workflow. Use when user wants to improve TBTA features, work on TBTA, or continue TBTA feature work.
phase-05-development-execution
Execute development in sprints with continuous quality. Sprint planning, code development, code reviews, security in development (shift left), unit testing, integration, and documentation.
project-analysis
A specialist skill that analyses a codebase to understand its structure, dependencies, and architecture. This skill should be used at the start of a new project or when onboarding to an existing codebase.
honest-reflections
Systematic gap analysis for claimed vs actual work completion. Uses 100+ sequential thoughts to identify assumptions, partial completions, missing components, and rationalization patterns. Validates completion claims against original plans, detects scope deviations, reveals quality gaps. Essential for self-assessment before declaring work complete. Use when: claiming completion, final reviews, quality audits, detecting rationalization patterns in own work.
executing-plans
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
openspec-to-beads
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with dependencies, discovers gaps, and maintains audit trail between planning and execution.
