Recalibrate time and effort estimates for engineering and coding tasks to reflect AI-agent execution speed instead of human-developer throughput. Consult this skill any time you are about to state how long an engineering or coding task will take — whenever you give an ETA, size a change, commit to a delivery, or emit any task/effort duration ("this will take 1-2 days", "a couple hours", "about a sprint", "ready by end of week"). Claude systematically overestimates engineering time by one to three orders of magnitude because its priors are calibrated on human developer productivity, not on how fast an agent actually executes — so use this even when the user did NOT explicitly ask "how long will this take". Also triggers on planning, roadmapping, sprint sizing, story points, effort/complexity estimation, deadlines, and phrases like "how long", "ETA", "when will this be done", "by [date]", "how much work is this". Scope: engineering/coding *execution* time — not a user's own manual effort, calendar scheduling, o
Techniques for writing comprehensive, self-contained prompts when spawning sub-agents or teammates via the Task tool. Use when delegating work to agents, designing multi-agent workflows, or when spawned agents are returning poor results due to insufficient context. Covers frontloading, file path enumeration, deliverable specification, constraint injection, and pattern reuse across spawn calls.
Analyze user objectives to identify and recommend the optimal set of skills, tools, and knowledge needed to complete tasks effectively. Provide skill gap analysis, pattern-based recommendations, and workflow design for complex tasks. This skill should be used when users need help determining what skills are required, when working on complex tasks requiring multiple capabilities, when detecting skill gaps or mismatches, or when designing skill ecosystems for workflows. Also use when users mention "what skills do I need", "skill discovery", "skill recommendation", "capability analysis", "skill gap", "which tools for this task", or "skill stack".
Protocol reference for delegated squad coordination. Defines the spawn request and completion report message formats that agents use to communicate within a delegated multi-agent squad. This skill should be used when agents need to send spawn requests, write completion reports, or understand the communication conventions of a delegated squad setup. Also use when you see terms like "spawn request", "completion report", "squad coordination", or "team message format".
Expert knowledge base of team organization patterns for multi-agent AI systems and software engineering. Provides pattern selection guidance for scenarios including incident response, greenfield design, legacy migration, security audits, performance optimization, API design, data pipelines, testing, documentation, and code migration. This skill should be used when designing agent teams, selecting team topologies, choosing communication patterns, sizing teams, or determining optimal team structure for a given situation. Also use when users mention "team pattern", "team topology", "agent coordination", "team design", "swarm configuration", "multi-agent architecture", "how many agents", or "what agents do I need".
Use for /collaboration, collaboration repair, friction signals, soft-skills coaching, or structured human-Claude interaction techniques such as compromise, rubber ducking, energy checks, pairing, retros, working agreements, and perspective swaps.
Run a structured human-Claude collaboration retrospective. Use for /therapist, therapy sessions, interaction reviews, workflow check-ins, frustration recovery, or improving how the user and Claude work together.
View or change context-awareness plugin configuration. Use this when the user asks to configure the settings for the context-awareness plugin, or when they ask to view the current configuration.