Spc Control Charts
>-
Writing Plans
Create a detailed, phased implementation plan from an approved spec. Use after brainstorming produces an approved spec. Produces a plan file that executing-plans or subagent-driven-development can consume.
Iatf 16949 Audit
>-
Five Whys
Root cause analysis using the Five Whys technique. Use when a bug persists despite surface fixes, a failure recurs, or a process keeps breaking. Ensures the fix targets the root, not the symptom.
Api Contract First
Hard gate before implementing any API endpoint or service interface. Requires a written, reviewed contract (OpenAPI 3.x, protobuf, or GraphQL schema) before any implementation code is written. Prevents breaking changes, misaligned clients, and undocumented behaviour.
Finishing A Development Branch
Complete a development branch before merge — verify tests pass, update documentation, ensure quality gate passes, and prepare a clean PR.
Systematic Debugging
Use when encountering any bug, test failure, or unexpected behavior. Enforces root-cause investigation before fixes. The Iron Law — no fixes without understanding why.
Brainstorming
Use BEFORE any creative work — creating features, building components, adding functionality. Explores user intent, requirements, and design before implementation. Hard-gated: no code until user approves the spec.
Skill Duplication Audit
A Claude skill from RBraga01/a-team.
Retention Design
Use before launching any new feature or product. Requires the activation moment, habit loop, and reactivation path to be designed before launch. Blocks "users will come back if they like it" completions.
Fmea Reviewer
>-
Ncr Writing
>-
Using A Team
The meta-skill. Loaded at every session start. Defines which A Team skills and agents MUST be used for which situations. If a skill or agent applies, you do not have a choice — you must use it.
Is Is Not Scoping
>-
Dfmea Design
>-
Msa Gauge Rr
>-
Car Corrective Action
>-
Skill Auditor
>-
Action Priority Ap
>-
Dmaic
>-
Ppap Checker
>-
Apqp
>-
8d Report Writing
>-
Control Plan
>-
Supplier Scar
>-
Control Plan Builder
>-
Dvp Test Plan
>-
Audit Guide
>-
Iso 9001 Internal Audit
>-
Ppap
>-
Pdca Improvement
>-
Pfmea Process
>-
Verification Before Completion
Use before claiming ANY task is complete. Requires you to run actual verification commands, read real output, and confirm it matches expectations — before stating the task is done. Blocks "should work" rationalizations.
Ncr Writer
>-
Rca Facilitator
>-
Fishbone Analysis
>-
8d Coach
>-
8d Problem Solving
>-
Subagent Driven Development
Use when executing implementation plans with independent tasks in the current session. Dispatches a fresh subagent per task with two-stage review (spec compliance, then code quality).
Using Git Worktrees
Create or verify an isolated git worktree before starting any development work. Prevents main branch contamination, enables parallel feature development, and gives subagents a clean baseline. Use at the start of every feature branch.
Executing Plans
Use when you have a written implementation plan to execute in the current session. Loads the plan, reviews critically, executes all tasks, and reports when complete.
Writing Skills
Create new A Team skills using TDD for documentation. Write a bad skill, watch agents fail at the gap, improve, iterate. Use when the team needs a new capability that no existing skill covers.
Positioning Audit
Use before any marketing copy is written for a product, feature, or campaign. Requires a clear category, a specific audience, and a differentiated claim — verified against the "so what?" test — before any copy is produced. Blocks "we'll develop the messaging as we write" completions.
Data Migration
Hard gate before any database schema change or data transformation in production. Requires a written migration plan with rollback strategy, dry run, and verification steps before execution. Prevents data loss, downtime, and irreversible schema changes.
Test Driven Development
Enforce RED-GREEN-REFACTOR discipline for every implementation task. Use for all new features, bug fixes, and refactors. The core rule — if you didn't watch the test fail, you don't know if it tests the right thing.
Smart Init
Conversational onboarding for A Team. Detects ROADMAP.md, extracts context, generates INIT.md without requiring technical knowledge. Invoked automatically by the orchestrator when INIT.md is missing.
Ab Test Design
Use before running any experiment that will inform a product decision. All six elements — hypothesis, metric, sample size, duration, stopping rule, and decision rule — must be defined before the test starts. Blocks "we'll stop when we see something" completions.
Vda 6 3 Audit
>-
Ai Feature Validation
Use before any AI feature is approved for build. Covers four AI-specific risks that standard PRD review misses: hallucination UX, trust calibration, scope creep, and reversibility. Blocks "we validated it like any other feature" completions.
User Research Synthesis
Use after conducting user research and before making product decisions from it. Requires every insight to map to a decision. Blocks "users said X" reports that produce no actionable direction.
Metric Definition
Use before writing any implementation code for a new feature. North star metric, guardrail metrics, and diagnostic metrics must be defined — with baselines — before the build begins. Blocks "we'll figure out the metrics from the data" completions.
Prompt Ux Design
Use when designing the user-facing prompt experience for any AI feature. Covers input design, suggestion patterns, history, feedback signals, and the interaction model between user intent and model execution.
Design Before Code
Use before implementing any new AI feature UI component. Requires a written shape/spec — layout, states, copy, interactions — before a single line of implementation code is written. Blocks "I'll design it as I build it" completions.
Ai Onboarding Design
Use when designing first-run flows and empty states for AI features. AI onboarding has specific requirements — model capability communication, trust building, and graceful degradation when the model doesn't know — that generic onboarding patterns miss.
Launch Plan Design
Use before launching any approved project, product, feature, or campaign externally. Requires launch goal, audience, offer, assets, channels, timeline, pre-launch and launch-day tasks, post-launch follow-up, success metrics, risks, and rollback criteria to be defined before launch day. Blocks "we'll figure out launch day as we go" completions.
Campaign Brief Generator
Use before any campaign moves from strategy to execution. Transforms a growth strategy and offer into an executable brief — campaign objective, audience, offer, message, channel, creative requirements, landing destination, CTA, success metric, review gates, and launch checklist. Blocks "the team knows what we're going for" completions.
Growth Strategy Design
Use before any copy, campaign, or experiment work begins on a new project or growth initiative. Requires growth stage, target segment, growth goal, primary constraint, channel hypothesis, core offer, north star metric, a 90-day hypothesis, and named risks to be defined before any execution starts. Blocks "let's just start running campaigns" completions.
Copy Quality Gate
Use before any external-facing copy ships. Applies three tests — "so what?", "who cares?", and "why now?" — to every claim in the copy. Blocks "it explains what we do" completions.
Channel Selection Audit
Use before building any campaign, content plan, or outbound motion. Scores every candidate growth channel against eight criteria — audience presence, intent, cost to test, feedback speed, trust requirement, sales cycle fit, operational complexity, and measurement feasibility — before one is chosen. Blocks "let's try everything" and "we picked the channel everyone else uses" completions.
Design Token Audit
Use before any AI feature UI lands in production. Every colour, spacing value, typography, shadow, and border in AI components must reference design tokens — no hardcoded values. Blocks "I'll align with the design system later" completions.
Ai Component Patterns
Use when designing or implementing any of the 6 core AI UI components. Each has specific patterns, pitfalls, and required sub-components that generic UI components don't address.
Ai Output Design
Use when designing how AI-generated content is rendered — streaming text, structured data, citations, code blocks, and uncertainty signals. Covers both visual rendering and the accessibility layer.
Offer Quality Gate
Use before any copy or campaign is built around an offer. Requires target customer, painful problem, promised outcome, mechanism, proof, risk reversal, pricing or exchange model, CTA, and objection handling to be defined before the offer is used in any external-facing work. Blocks "the offer is implied by the product" completions.
Dispatching Parallel Agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Dispatches one focused agent per problem domain, runs them concurrently, then integrates.
Ai Messaging Review
Use before any AI product messaging ships externally. Audits capability claims for accuracy, quantified claims for evidence, and "AI" labels for specificity. Blocks "10x productivity" without measurement and "AI-powered" without definition.
Funnel Analysis
Use before beginning any conversion rate optimisation effort. Requires the leak to be identified and root-caused before any solution is proposed. Blocks "let's improve our conversion rate" without knowing which step breaks.
Performance Audit
Systematic performance investigation workflow. Use when performance regressions are suspected, before and after optimisation work, or as a pre-release gate for performance-critical features. Produces a baseline, identifies the real bottleneck, and validates improvement with hard numbers.
Experiment Design
Use before running any growth experiment — pricing test, copy variant, onboarding flow, feature gate — that will inform a ship/no-ship decision. All six elements must be defined before the test starts. Blocks "we'll run it for a while and see" completions.
Feature Scoping
Use before any engineering estimate is made. Requires a written scope before an estimate, and a written estimate before a commit. Blocks "we'll scope as we go" and "just give me a rough number" completions.
Prd Quality Gate
Use before committing scope, estimate, or engineering time to any feature. Requires user problem, success metric, scope boundary, and anti-goals defined before any estimate is made. Blocks "we'll define success once we see the data" completions.
Pricing Page Review
Use before publishing or changing any pricing, packaging, or plan page. Reviews pricing clarity, plan differentiation, target customer per tier, CTA clarity, risk reversal, objections, comparison logic, anchoring, limitations, upgrade path, and trust/proof. Blocks "the pricing speaks for itself" completions.
Accessible Ai Output
Use before shipping any UI that renders AI-generated content. Dynamic model output requires ARIA live regions, reading order, and cognitive load review that static content does not. Blocks "we'll do accessibility later" completions.
Ai States Required
Use before writing any code for an AI feature's UI. All 7 states must be designed and documented before implementation begins. Blocks "we'll add loading states later" completions.
5why Root Cause
>-
Incident Response
Production incident playbook. Use immediately when production is degraded or down. Five phases: detect, contain, diagnose, resolve, post-mortem. Prevents the chaos of uncoordinated response and ensures every incident produces lasting improvements.
Social Proof Review
Use before any testimonial, case study, logo, quantified result, screenshot, review, or before/after claim is used in marketing. Verifies source, context, permission, and accuracy for every piece of proof. Blocks "this looks credible enough" completions and unsourced or misleading proof.
Mvp Scope Validator
Use before writing a PRD for a new product or feature. Extracts the core hypothesis and reduces scope to the minimum needed to test it. Blocks feature lists that bundle multiple unvalidated assumptions.
Growth Metrics Design
Use before executing any growth initiative — campaign, launch, or experiment. Requires north star metric, input/output metrics, leading/lagging indicators, activation/retention/conversion metrics, measurement cadence, minimum viable tracking, and a named owner per metric to be defined before execution starts. Blocks "we'll know growth is working when we see it" completions.