Development & Workflow Planning Skills

Use when the user says "arness code assess", "arn-code-assess", "assess codebase", "technical review", "codebase assessment", "find improvements", "what should I improve", "tech debt review", "tech debt audit", "pattern compliance check", "codebase health check", "assess the project", "improvement plan", "review my codebase", "what needs fixing", "code quality check", "audit my code", "run an assessment", or wants a comprehensive technical assessment of the codebase against stored patterns followed by prioritized improvement execution through the full Arness pipeline.

Use when the user says "batch planning", "batch plan", "arness batch planning", "arn-code-batch-planning", "plan multiple features", "plan all features", "plan unblocked features", "plan the backlog", "plan from backlog", "batch spec and plan", "plan next features", "sequential planning", "multi-feature plan", "plan the next batch", "plan these features", "batch plan GitHub issues", "batch plan from Jira", "plan issues in batch", or wants to plan multiple features from the greenfield Feature Tracker, GitHub issues, or Jira issues in a single session. Pre-analyzes all selected features in parallel, then guides sequential spec review with pipelined plan generation. This skill is typically invoked directly or after arn-brainstorming completes and chains to arn-code-batch-implement upon completion. For single-feature planning, arn-planning is the correct entry point.

Use when the user says "feature spec", "arness code feature spec", "arn-code-feature-spec", "spec this feature", "help me spec", "design this feature", "feature design", "write a spec", "create a specification", "I have an idea for a feature", "let's flesh out this feature", "decompose feature", "spec XL feature", "resume spec", "continue spec", "finish my spec", "break down feature", or wants to iteratively develop a feature idea into a well-formed specification through guided conversation with architectural analysis. For XL features with decomposition hints, creates multiple sub-feature specs with full traceability. Produces specification documents capturing WHAT to build and WHY, which then feed into plan creation.

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.

Use when the user says "arness code plan", "arn-code-plan", "plan this", "write a plan", "create plan", "implementation plan", "plan feature", "plan the spec", "plan from spec", "generate plan", "arness code plan FEATUREX", "plan the bugfix", "plan bugfix", "make a plan", or wants to generate an implementation plan from a Arness specification. The skill invokes the arn-code-feature-planner agent to generate the plan, presents it for review, and iterates on user feedback until approved. Produces a PLANPREVIEW file that feeds into /arn-code-save-plan.

Use when the user says "save plan", "save the plan", "arness code save plan", "structure this plan", "create project from plan", "export plan", "export project plan", "organize this plan", "set up project structure", "turn this into a project", "generate project structure", "finalize the plan", or wants to convert a planning conversation into an actionable phased project structure with implementation and testing plans.

Use when the user says "ship it", "arness code ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", or wants to commit, push, and optionally open a pull request. Guides through branching, staging, committing with meaningful messages, pushing, and PR creation. Works standalone or as the final Arness pipeline step. Do NOT use this for reviewing PRs — use /arn-code-review-pr for that.

Use when the user says "sketch", "arness code sketch", "preview this", "show me what this looks like", "UI preview", "sketch the feature", "visual preview", "sketch this page", "what will this look like", "mock this up", "prototype this UI", "preview the design", "sketch the UI", "preview this command", "show me what the output looks like", "sketch the TUI", "what will the CLI look like", "mock up the terminal output", or wants to see a working interface preview of a feature in the context of their existing application before committing to full implementation. Creates real, runnable artifacts using the project's actual framework and conventions, rendered in a dedicated sketch namespace.

Use when the user says "standard", "standard mode", "standard implementation", "arn-code-standard", "standard change", "medium change", "standard feature", "standard fix", or wants a mid-ceremony implementation for a change that needs lightweight architectural context (spec-lite) and task-tracked execution but not the full feature-spec/plan pipeline. Bridges the gap between arn-code-swift and the full thorough pipeline. Includes spec-lite generation, structured plan, in-session execution, review-lite, and a unified change record.

Use when the user says "swift", "arness code swift", "quick change", "small change", "just do this", "quick feature", "quick implementation", "swift fix", "implement this quickly", "add this quickly", "simple change", "just implement this", "arn-code-swift", "swift mode", "quick task", or wants a lightweight, pattern-aware implementation for a small feature or enhancement (1-8 files) without going through the full Arness pipeline. Bridges the gap between raw Claude Code and the full feature-spec/plan pipeline. Includes architectural assessment, targeted testing, and pattern compliance review.

Use when the user says "taskify", "create task list", "create tasks", "convert plan to tasks", "generate tasks from plan", "create tasks from plan", "turn plan into tasks", "arness code taskify", or wants to convert a structured project plan's TASKS.md into an executable Claude Code task list with proper dependency management.

Use when the user says "containerize", "dockerize", "create dockerfile", "docker setup", "container setup", "arn infra containerize", "infra containerize", "generate docker", "docker compose", "compose setup", "containerize my app", "docker configuration", "create docker-compose", "multi-stage docker", "container config", "dockerize my application", "infra docker", "set up containers", or wants to generate Dockerfiles, docker-compose configurations, and .dockerignore files for their application with security auditing and multi-stage build best practices.

Optional customization tool for infrastructure projects. This skill should be used when the user says "infra init", "arn infra init", "initialize infra", "setup infrastructure", "arn-infra-init", "configure infra", "init infra", "infrastructure setup", "set up infrastructure", "infra setup", "start infra", "configure arn infra", "add infrastructure to this project", "review infra config", "customize infra config", "infra settings", or wants to configure providers, environments, IaC tools, CI/CD platform, or review current infrastructure settings. Arness Infra auto-configures with sensible defaults on first skill invocation — this init is optional for basic usage but required for provider/environment configuration.

Use when the user says "planning", "arness planning", "plan a feature", "start planning", "I want to build", "new feature", "plan something", "what should I build", "pick an issue", "plan a bug fix", "I have an idea", "spec and plan", "plan from scratch", "plan this", "feature planning", "bug planning", "plan this issue", "arn-planning", or wants to go from an idea, issue, or bug report through to a complete implementation plan ready for execution. Handles severity-aware scope routing across three ceremony tiers (swift, standard, thorough), routing between feature specs, bug specs, and quick implementations, and produces a reviewed plan ready for execution. Chains to arn-implementing at completion.

Use when the user says "clickable prototype teams", "arn clickable prototype teams", "team clickable prototype", "debate clickable prototype", "collaborative interaction review", "clickable prototype with debate", "team-based interaction review", "interaction debate", "review interactions as a team", "interactive prototype teams", "team prototype review", or wants to create a clickable interactive prototype with linked screens and validate it through iterative expert debate cycles where product strategist and UX specialist discuss their scores and findings before producing a combined review, with Playwright-based interaction testing, per-criterion scoring, an independent judge verdict, and versioned output. Supports Agent Teams for parallel debate or sequential simulation as fallback. For standard lower-of-two-scores interaction review, use /arn-spark-clickable-prototype instead.

Use when the user says "discover", "product discovery", "arn discover", "help me define this product", "what should I build", "product concept", "define the product", "let's figure out what to build", "vision for this project", "shape this idea", "new project idea", "brainstorm this product", "starting from scratch", or wants to explore and structure a greenfield product idea through guided conversation. Produces a product-concept.md document capturing the product vision, core experience, target users, trust model, platforms, and scope boundaries.

Use when the user says "feature extract", "arn feature extract", "extract features", "feature backlog", "create backlog", "list features", "what features do we need", "prioritize features", "feature list", "build the backlog", "what should we build", "upload features", "feature tracker", or wants to extract a structured, prioritized feature list with journey steps, validated components, use case context, and UI behavior details from all project artifacts, producing a feature backlog document with a Feature Tracker that bridges into arn-code-feature-spec and optionally uploads features to the issue tracker.

Optional customization tool for greenfield projects. This skill should be used when the user says "greenfield init", "arn spark init", "initialize greenfield", "setup greenfield", "greenfield setup", "start greenfield", "configure greenfield", "set up greenfield", "init greenfield", "greenfield configuration", "review greenfield config", "customize greenfield config", "greenfield settings", "Figma setup", "Canva setup", "add Figma", "add Canva", "design tool setup", or wants to customize Arness Spark configuration, add design tool integrations (Figma, Canva), or review current greenfield settings. Arness Spark auto-configures with sensible defaults on first skill invocation — this init is optional. Design tool integration (Figma/Canva) remains available only through this skill.

Use when the user says "static prototype teams", "arn static prototype teams", "team static prototype", "debate static prototype", "collaborative visual review", "static prototype with debate", "team-based visual review", "visual debate", "review visuals as a team", or wants to create a static component showcase and validate it through iterative expert debate cycles where product strategist and UX specialist discuss their scores and findings before producing a combined review, with per-criterion scoring, an independent judge verdict, and versioned output. Supports Agent Teams for parallel debate or sequential simulation as fallback. For standard lower-of-two-scores visual review, use /arn-spark-static-prototype instead.

Use when the user says "competitive analysis", "gap analysis", "competitive gap", "stress competitive", "compare competitors", "feature comparison", "competitive stress test", "market comparison", "competitor analysis", or wants to stress-test a product concept by conducting deep competitive gap analysis with feature comparison, gap identification, and positioning assessment. Produces a competitive report with a feature matrix, per-competitor analysis, and recommended concept updates.