This skill provides guidance on accessing session data efficiently in ultrawork. Covers JSON vs Markdown rules, token efficiency rationale, and common patterns. Required knowledge for all ultrawork agents (explorer, planner, worker, verifier, reviewer).
Use when setting up a new open-ended goal for autonomy tracking, before starting the first iteration
Evidence-based verification checklist before marking work complete. Use before PRs, releases, marking tickets done, or any "I'm finished" declaration.
Generate implementation plans FROM specifications - reads spec as input, extracts requirements, creates step-by-step tasks with validation against spec
Document the critical business logic for load lifecycle and billing workflows in laneweaverTMS. Use when implementing load status transitions, billing workflows, financial calculations, TONU handling, or quick pay features.
Human verification checklist for generated schedules. Use when reviewing Block 10 or any generated schedule to ensure it makes operational sense. Covers FMIT, call, Night Float, clinic days, and absence handling.
Special educational guardrail. Activated when the student is rushing, asking for too much automation, or showing lack of understanding of engineering principles.
Monitor workload definitions, distribution, and TASM statistics using real-time resources to understand classification effectiveness and workload performance
Block time for focused work using calendar-based time management strategies
Plan and organize multi-project initiatives. Use when work spans multiple services, repositories, or has natural project boundaries.
Reject complacency. Demand excellence. Ship or die.
Use when reviewing, validating, or checking story documents. Triggers on requests to review stories, validate requirements, or check story readiness.
[Code Quality] Defines clear boundaries and goals for a refactoring session. Use to establish what WILL and WILL NOT change, set success criteria, and create a focused refactoring scope.
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
Executes development tasks from a master plan (00-PLAN.md). Accepts optional feature name/path parameter. Reads the plan, identifies the next pending task, confirms with user, executes it, and updates all relevant documentation. Use when implementing features step-by-step or when user says "execute next task [feature-name]", "continue implementation", or "what's next?".
You are a highly organized and unflappable Studio Producer. You are the operational backbone of a creative studio, managing the flow of projects, resources, and client communications. You are a master of budgets, timelines, and making sure the creative team has everything they need to do their best work.
Create or update a structured plan directory with a PLAN.md index and numbered task files (001-*.md) containing checklists, tests, and completion criteria.
Prepare board meeting decks, updates, and materials for effective governance
Mark a plan as completed and archive it. Use this when you've finished implementing all items in a plan document.
Enterprise Skill for advanced development
Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.
Document root cause analysis for team learning. Blameless, actionable, preventive.
Create comprehensive project plans with timelines, dependencies, and resource allocation
