full-team

Plugin full-team from marketplace tonone-ai in tonone-ai/tonone. Commands read from the repo's manifest — 2 days ago.

Skills (173)

• apex-decisions

  Append-only log of settled project decisions and learnings, shown at session start. Use when asked to "log this decision", "record that we decided", "supersede decision", "what did we decide", "/learn", "remember this lesson", or "show learnings".

• apex-guard

  Opt-in session guard that confirms destructive commands and freezes edits to one directory. Use when asked to "be careful", "freeze edits to src/", or "guard this session".

• apex-plan

  Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

• apex-recon

  Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

• apex-retro

  Weekly engineering retrospective from git history. Use when asked to "retro", "what did we ship this week", or "weekly retrospective".

• apex-review

  Cross-cutting multi-lens review of a diff — parallel security/backend/data/test lenses, red-team pass, merged verdict. Use when asked to "review what we built", "check the work", "pre-launch review", or "red-team this diff". Not the skill-manifest gate.

• apex-second-opinion

  Optional cross-model review of a diff or plan through an external CLI (codex, gemini, llm) already on PATH, with redaction and per-run consent. Use when asked for "a second opinion", "cross-model review", or "have codex/gemini look at this".

• apex-skillify

  Turn a flow that just worked in this session into a reusable skill. Use when asked to "skillify this", "make this a skill", or "save this workflow".

• apex-status

  CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

• apex-takeover

  System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

• atlas-adr

  Write an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".

• atlas-changelog

  Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

• atlas-map

  Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".

• atlas-onboard

  Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

• atlas-present

  Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".

• atlas-recon

  Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

• atlas-report

  Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

• buzz-community

  Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program

• buzz-launch

  Design and execute a launch plan — Product Hunt, HN Show HN, newsletter coordination, social posts, and community launch moment. Use when asked to "launch [feature/product]", "plan a launch", "help us do a Product Hunt launch", or "coordinate the announcement".

• buzz-pitch

  Write media pitches and press releases — journalist outreach emails, podcast pitch scripts, newsletter sponsor pitches, and press release copy. Use when asked to "pitch journalists", "write a press release", "reach out to podcasts", or "get media coverage".

• buzz-recon

  PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.

• buzz-social

  Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".

• copy-slop

  Run the deterministic copy-slop check on drafts or UI strings: AI-tell words, residue, em-dash and contrast-frame overuse, with waivers for client terms. Use when asked to "check for AI slop", "does this sound like AI", "run the slop check", or "lint this copy".

• cortex-eval

  Evaluate model performance — check for accuracy drops, data drift, and error patterns. Use when asked about "model accuracy dropped", "evaluate the model", "check for drift", or "model performance".

• cortex-integrate

  Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".

• cortex-model

  Build an ML pipeline — from data to trained model to serving endpoint. Use when asked to "build ML model", "train a model", "prediction pipeline", "classification", or "regression".

• cortex-prompt

  Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".

• cortex-recon

  ML reconnaissance — inventory all models, pipelines, data sources, and monitoring. Use when asked "what ML do we have", "model inventory", or "ML assessment".

• crest-compete

  Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".

• crest-narrative

  Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

• crest-okr

  OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".

• crest-recon

  Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap

• crest-roadmap

  Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".

• cut-fetch

  Fetch licensed real photos and icons by subject, with credits recorded. Use when asked to "find a photo of", "get an icon for", "fetch stock imagery", or "source real assets". Local files only, per-asset licence record, refuses unclear licences.

• deal-close

  Close a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answ

• deal-pipeline

  Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".

• deal-playbook

  Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".

• deal-pricing

  Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".

• deal-recon

  Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".

• deal-signals

  Signal-based prospecting — read target companies' public sites for buying signals (ads, incumbent agency, tech stack, hiring) with evidence URLs, then build a cohort. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", or "build a target list from t

• draft-flow

  Use when asked to design a user flow, map how a user moves through a feature, create a wireframe or flow diagram, or document interaction design for a product brief. Examples: "design the flow for X", "map out the user journey", "create a wireframe for this feature", "how should the UX work for this

• draft-ia

  Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hi

• draft-recon

  UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wirefra

• draft-review

  Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".

• draft-wireframe

  Wireframe a screen — buildable ASCII spec by default (Form and Prism can act on it), or a hand-drawn single-file HTML whiteboard look when the user says "sketch", "hand-drawn", "lo-fi HTML", or "visual wireframe".

• echo-feedback

  Feedback synthesis — cluster support tickets, NPS verbatims, app reviews, and churn surveys by theme into an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", or "NPS analysis".

• echo-interview

  Run a user interview — produce an interview guide and synthesize output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", or "build a persona from this feedback".

• echo-jobs

  Jobs-to-Be-Done analysis — from a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", or "why are users switching".

• echo-panel

  Synthetic stakeholder panel — grounded personas react to a launch, pricing change, PRD, or message; returns ranked objections and messages to test. Use when asked to "simulate how users will react", "test this launch with a synthetic panel", "focus group this", or "pressure-test this message".

• echo-recon

  User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or

• echo-segment

  User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user".

• flux-health

  Data quality and pipeline health check — freshness, schema drift, null rates, orphaned records, pipeline status. Use when asked about "data quality check", "pipeline health", "is our data fresh", or "schema drift".

• flux-migrate

  Build zero-downtime database migrations — forward SQL, rollback SQL, deployment sequence. Use when asked to "write migration", "schema change", "add column", "rename table", "drop column", or "migrate safely".

• flux-pipeline
• flux-query
• flux-recon
• flux-schema
• forge-audit
• forge-cost
• forge-diagnose
• forge-infra
• forge-network
• forge-recon
• form-audit
• form-bolder
• form-brand
• form-brief
• form-component
• form-critique
• form-deal
• form-deck
• form-direction
• form-distill
• form-document
• form-email
• form-lint
• form-logo
• form-mobile
• form-polish
• form-quieter
• form-social
• form-tokens
• form-web
• helm-arbiter
• helm-autoplan
• helm-brief
• helm-handoff
• helm-init
• helm-office-hours
• helm-plan
• helm-recon
• ink-calendar
• ink-case
• ink-post
• ink-recon
• ink-seo
• keep-expand
• keep-health
• keep-onboard
• keep-playbook
• keep-recon
• lens-audit
• lens-dashboard
• lens-metrics
• lens-recon
• lens-report
• lumen-abtest
• lumen-funnel
• lumen-instrument
• lumen-metrics
• lumen-recon
• move-moments
• pave-audit
• pave-catalog
• pave-env
• pave-golden
• pave-recon
• pitch-copy
• pitch-launch
• pitch-message
• pitch-position
• pitch-recon
• prism-audit
• prism-component
• prism-dashboard
• prism-extract
• prism-harden
• prism-recon
• prism-redesign
• prism-ui
• prism-variants
• proof-api
• proof-audit
• proof-e2e
• proof-recon
• proof-strategy
• relay-audit
• relay-deploy
• relay-docker
• relay-pipeline
• relay-recon
• spine-api
• spine-design
• spine-perf
• spine-recon
• spine-review
• spine-service
• surge-activation
• surge-experiment
• surge-plg
• surge-recon
• surge-retention
• tonone-doctor
• touch-app
• touch-audit
• touch-feature
• touch-recon
• touch-release
• vigil-alert
• vigil-check
• vigil-incident
• vigil-instrument
• vigil-recon
• volt-driver
• volt-firmware
• volt-ota
• volt-power
• volt-recon
• warden-audit
• warden-harden
• warden-iam
• warden-recon
• warden-threat

Subagents (27)

• apex

  Engineering lead — orchestrates the team, scopes work, controls depth and budget

• atlas

  Knowledge engineer — architecture docs, ADRs, API specs, system diagrams, onboarding

• buzz

  PR & Community engineer — press pitches, social media, open source community, DevRel, and coordinated launch moments

• cortex

  ML/AI engineer — LLM integration, prompt engineering, RAG, evals, and AI feature design for production

• crest

  Product strategist — diagnosis-first strategy, roadmap sequencing, competitive positioning, and market decisions

• deal

  Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing

• draft

  UX designer — user flows, information architecture, wireframes, and interaction design

• echo

  User researcher — interviews, personas, Jobs-to-Be-Done, and customer feedback synthesis

• flux

  Data engineer — databases, migrations, pipelines, data modeling

• forge

  Infrastructure engineer — cloud services, networking, IaC, cost optimization

• form

  Visual designer — brand identity, color systems, typography, UI design, and design systems

• helm

  Head of Product — product strategy, requirements, and engineering handoff via the Helm↔Apex interface

• ink

  Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar

• keep

  Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth

• lens

  Data analytics & BI engineer — dashboards, metrics design, reporting, data storytelling

• lumen

  Product analyst — metrics architecture, funnel analysis, A/B test design, retention, and growth measurement

• pave

  Platform engineer — developer experience, golden paths, service catalogs, environment management, internal tooling. Builds what removes friction for the team that exists.

• pitch

  Product marketer — positioning, messaging, value proposition, GTM strategy, and launch copy

• prism

  Frontend & DX engineer — translates Form's design system into production UI components, pages, and internal tools

• proof

  QA & testing engineer — test strategy, E2E suites, integration testing, test infrastructure, flaky test triage

• relay

  DevOps engineer — CI/CD, deployments, GitOps, developer experience

• spine

  Backend engineer — APIs, system design, performance, distributed systems

• surge

  Growth engineer — acquisition channels, activation funnels, retention playbooks, and PLG strategy

• touch

  Mobile engineer — native iOS/Android, cross-platform, app stores, mobile performance

• vigil

  Observability & reliability engineer — SLOs, alerting, instrumentation, incident response. Writes configs and runbooks, doesn't produce roadmaps.

• volt

  Embedded & IoT engineer — firmware architecture, microcontrollers, OTA updates, edge computing, device protocols

• warden

  Security engineer — IAM, secrets, threat modeling, hardening, auth, and supply chain security

Hooks (3)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/team/apex/hooks/apex-decisions.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/team/apex/hooks/apex-guard.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/team/form/hooks/form-design-lint.js"

Similar plugins