arness

arn-code-pick-issue

This skill should be used when the user says "pick issue", "work on issue", "arness code pick", "arness code pick issue", "arn-code-pick-issue", "grab issue", "pick from backlog", "what should I work on", "show issues", "find issue", "browse issues", "next issue", "select issue", "choose issue", "what's unblocked", "work on next feature", "pick from feature tracker", or wants to browse issues filtered by Arness labels, select one, and route it to the appropriate Arness pipeline skill for implementation. Supports local-first dependency resolution from a greenfield feature backlog when available. Requires an issue tracker (GitHub or Jira) to be configured for remote issue browsing. Do NOT use this for creating new issues — use /arn-code-create-issue for that.

arn-spark-naming

This skill should be used when the user says "naming", "brand name", "name my product", "find a name", "product naming", "brand naming", "what should I call it", "name ideas", "pick a name", "naming session", "help me name this", "brainstorm names", "come up with a name", "arn spark naming", "arn-spark-naming", or wants to find a brand name for their product through strategic analysis, creative generation, qualitative scoring, and due diligence including domain availability and trademark screening.

arn-code-catch-up

This skill should be used when the user says "catch up", "catch-up", "arness code catch up", "retroactive docs", "document old commits", "backfill artifacts", "what did I miss", "undocumented commits", "catch up on commits", "document past work", "backfill records", or wants to retroactively document commits that were made outside the Arness pipeline.

arn-code-bug-spec

This skill should be used when the user says "bug spec", "arness code bug spec", "investigate this bug", "help me debug", "trace this bug", "diagnose this issue", "I found a bug", "something is broken", "why is X not working", "fix this bug", "debug this", "why is this not working", or wants to iteratively investigate a bug through guided conversation with diagnostic analysis. Bridges the gap between a bug report and either a direct fix or a structured bug specification for the Arness pipeline.

arn-code-execute-plan-teams

This skill should be used when the user says "execute plan with teams", "run plan teams", "execute with agent teams", "team execution", "execute plan with agent teams instead of subagents", "teams mode", "agent teams mode", "execute with teams", or wants to execute a structured project plan using Claude Code's experimental Agent Teams feature. Creates a team of executor, reviewer, and architect teammates that collaborate on task implementation with built-in quality gates. Requires the experimental Agent Teams feature to be enabled. For standard subagent-based execution, use arn-code-execute-plan instead.

arn-code-help

This skill should be used when the user says "arness code help", "where am I", "what's next", "show pipeline", "pipeline status", "what step am I on", "arness code status", "arn-code-help", "show workflow", or wants to see their current position in the Arness workflow pipeline and get guidance on the next step.

arn-code-report

This skill should be used when the user says "report issue", "arness code report", "code report", "something went wrong", "report a bug", "file arness code issue", "arness code broke", "report arness code problem", "diagnose issue", "arness doctor", "run doctor", "diagnose arness code", "arn-code-report", or wants to report a problem with an Arness Code workflow skill. Invokes the arn-code-doctor agent to diagnose the issue, then files a GitHub issue on the Arness plugin repository. Do NOT use this for filing issues on the user's own project — use /arn-code-create-issue for that. For Spark issues use /arn-spark-report. For Infra issues use /arn-infra-report.

arn-code-ensure-config

This skill should be used when the user says "ensure config", "check arness config", "arn-code-ensure-config", "verify arness setup", or wants to verify that Arness Code configuration is present for the current project. This skill is primarily consumed as a reference by entry-point skills (arn-planning, arn-implementing, arn-shipping, arn-reviewing-pr, arn-assessing, arn-code-feature-spec, arn-code-bug-spec, arn-code-swift, arn-code-standard) which read the ensure-config reference as Step 0 before proceeding with their workflow.

arn-code-simplify

This skill should be used when the user says "simplify", "arness code simplify", "simplify code", "code simplification", "clean up code", "reduce complexity", "remove duplication", "check for reuse", "find duplicates", "optimize code", "efficiency review", "simplify implementation", "arn-code-simplify", or wants to review recently implemented code for reuse opportunities, quality issues, and efficiency problems after execution completes. Do NOT use this for full implementation correctness review (use arn-code-review-implementation) or PR review (use arn-code-review-pr).

arn-spark-help

This skill should be used when the user says "spark help", "arn spark help", "greenfield status", "greenfield help", "where am I in spark", "what's next for spark", "spark pipeline", "spark status", "arn-spark-help", "show spark pipeline", "what step am I on for spark", "spark workflow", "exploration status", "show exploration pipeline", "how does spark work", "explain spark pipeline", or wants to see their current position in the Arness Spark exploration pipeline and get guidance on the next step.

arn-spark-scaffold

This skill should be used when the user says "scaffold", "arn scaffold", "set up the project", "create project", "initialize project", "bootstrap project", "create the skeleton", "install dependencies", "configure the project", or wants to create a working project skeleton from architecture decisions with installed dependencies, configured build tools, and a UI toolkit ready for development.

arn-spark-static-prototype

This skill should be used when the user says "static prototype", "arn static prototype", "visual validation", "pixel perfect", "component showcase", "static screens", "build a static prototype", "create a component showcase", "visual review", "validate the visuals", "check the design", "validate components", "review the design visuals", or wants to create a static component showcase and validate it through iterative expert review cycles with per-criterion scoring, an independent judge verdict, and versioned output.

arn-spark-concept-review

This skill should be used when the user says "concept review", "review concept", "update product concept", "synthesize stress tests", "stress test review", "apply stress test findings", "review stress test results", "concept update", "merge stress test recommendations", or wants to synthesize findings from completed stress tests into a reviewed and updated product concept document. Scans for stress test reports, consolidates recommendations, resolves conflicts using product pillars, presents the full changeset for user approval, and produces an updated product-concept.md alongside a concept-review-report.md.

arn-implementing

This skill should be used when the user says "implementing", "arness implementing", "start implementing", "execute the plan", "build it", "implement this", "run the tasks", "execute", "start building", "implement the feature", "implement the fix", "quick change", "swift", "swift mode", "quick implementation", "standard", "standard mode", "standard implementation", "start execution", "build the feature", "arn-implementing", or wants to execute an implementation plan, run a quick implementation, a standard-tier implementation, or manage the build-simplify-review cycle. Chains to arn-shipping at completion.

arn-spark-dev-setup

This skill should be used when the user says "dev setup", "arn spark dev setup", "development environment", "configure dev environment", "dev container", "configure CI", "set up CI", "onboard developer", "developer setup", "set up docker", "configure development", "how do I set up this project", "development setup", "onboard me", "get this project running", "set up my machine", "new developer setup", "how do I get started", "developer onboarding", or wants to define a standardized development environment for their project (producing dev environment infrastructure files and a dev-setup document) or follow an existing environment standard to get onboarded as a new developer.

arn-spark-spike

This skill should be used when the user says "spike", "arn spike", "validate risks", "technical validation", "proof of concept", "validate architecture", "risk spike", "test this risk", "will this work", "technical spike", "validate the stack", or wants to validate critical technical risks from the architecture vision by creating minimal proof-of-concept code and testing whether the chosen technologies work as expected.

arn-spark-use-cases

This skill should be used when the user says "use cases", "arn use cases", "write use cases", "define use cases", "Cockburn use cases", "actor goals", "behavioral requirements", "system behavior", "what does the app do", "describe the behavior", "use case document", "document the behavior", "define system behavior", or wants to create structured use case documents that describe the application's behavior from actor perspectives, producing a use-cases/ directory with individual Cockburn fully-dressed use case files and a README index.

arn-brainstorming

This skill should be used when the user says "brainstorming", "arn brainstorming", "brainstorm", "let's brainstorm", "start brainstorming", "brainstorming session", "greenfield wizard", "arn spark wizard", "greenfield pipeline", "walk me through greenfield", "guided greenfield", "full greenfield pipeline", "greenfield flow", "explore to feature backlog", "greenfield start to finish", "run the greenfield pipeline", "guide me through greenfield", "greenfield guided mode", "greenfield setup", "new project wizard", "add a feature", "new feature", "I need another feature", "add feature to greenfield", "one more feature", or wants to be walked through the entire Arness greenfield exploration pipeline in a single continuous session with guided decision gates instead of invoking each skill manually. Also triggers when the user wants to add a new feature to an existing greenfield project after the clickable prototype is complete.

arn-code-init

Optional customization and upgrade tool. This skill should be used when the user says "initialize arness code", "arness code init", "arn-code-init", "init arness code", "setup arness code", "arness code setup", "set up arness code", "start arness code", "upgrade arness code", "update arness code", "configure arness code for this project", "add arness code to this project", "reconfigure arness code", "review arness config", "customize arness config", "arness settings", or wants to customize Arness configuration, review current settings, or upgrade after a plugin update. Handles both existing codebases (analyzes patterns) and greenfield projects (recommends patterns based on technology choices). Also handles upgrades after plugin updates.

arn-spark-visual-strategy

This skill should be used when the user says "visual strategy", "arn visual strategy", "visual testing", "visual regression", "screenshot testing", "compare to prototype", "visual validation", "how do I test visuals", "set up visual tests", "baseline images", "screenshot comparison", "pixel diff", "visual diff", "does it match the prototype", or wants to set up visual regression testing for development — creating capture scripts, comparison scripts, and baseline images so that feature implementations are automatically compared against prototype screenshots to catch visual regressions during development.

arn-assessing

This skill should be used when the user says "assessing", "arness assessing", "assess", "assess codebase", "technical review", "codebase assessment", "find improvements", "what should I improve", "tech debt review", "pattern compliance check", "codebase health check", "improvement plan", "review my codebase", "what needs fixing", "code quality check", "audit my code", "run an assessment", "arn-assessing", or wants a comprehensive technical assessment of the codebase against stored patterns followed by prioritized improvement execution. Chains to arn-implementing if improvements are identified.

arn-code-batch-implement

This skill should be used when the user says "batch implement", "implement all", "batch execution", "implement all features", "parallel implement", "implement in parallel", "arness batch implement", "arn-code-batch-implement", "run batch implementation", "implement everything", "launch batch workers", or wants to spawn parallel worktree-isolated background agents to implement multiple pending features simultaneously. Each worker runs as a full independent session with all tools. This skill requires pending plans in .arness/plans/ — run arn-code-batch-planning first if none exist.

arn-infra-execute-change

This skill should be used when the user says "execute infra change", "run infra plan", "apply infrastructure change", "execute change", "arn infra execute", "deploy infra plan", "execute infrastructure plan", "run infrastructure change", "apply infra plan", "infra execute", "arn-infra-execute-change", or wants to orchestrate the phased execution of a structured infrastructure change plan, invoking agents for IaC generation, security gates, cost gates, deployment, verification, and review.

arn-infra-migrate

This skill should be used when the user says "migrate infrastructure", "arn infra migrate", "infra migrate", "move to AWS", "move to GCP", "move to Azure", "switch providers", "change cloud provider", "graduate from PaaS", "move from heroku", "move from fly.io", "consolidate providers", "infrastructure migration", "provider migration", "partial migration", "move database", "move services", "arn-infra-migrate", "infrastructure move", "cloud migration", or wants to migrate infrastructure between providers, graduate from PaaS to IaC, consolidate providers, or partially move specific services.

arn-infra-save-plan

This skill should be used when the user says "save infra plan", "save infrastructure plan", "structure infra plan", "create infra project", "finalize infra plan", "arn infra save plan", "infra save plan", "save change plan", "structure infrastructure plan", "finalize infrastructure plan", "arn-infra-save-plan", or wants to convert a PLAN_PREVIEW_INFRA_*.md into a structured project directory with infrastructure-specific templates, report templates, and progress tracking.