From arn-code
Detects current position in Arness code workflow pipeline, renders ASCII diagram with active stage marked, and suggests next command. Supports Arness Spark and Infra cross-plugin awareness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/arn-code:arn-code-helpThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Detect the user's current position in the Arness workflow pipeline, render an ASCII diagram with the active stage marked, and suggest the next command to run. Supports cross-plugin awareness — detects activity in Arness Spark and Arness Infra and provides hints at the bottom of the output. This skill is strictly read-only -- it never modifies files or project state.
Detect the user's current position in the Arness workflow pipeline, render an ASCII diagram with the active stage marked, and suggest the next command to run. Supports cross-plugin awareness — detects activity in Arness Spark and Arness Infra and provides hints at the bottom of the output. This skill is strictly read-only -- it never modifies files or project state.
Allowed tools: Read, Glob, Grep only. This skill MUST NOT use Write, Edit, Bash, or Task tools. This skill MUST NOT invoke any agents.
## Arness section (loaded in Step 1), detect other plugin field groups:
Vision directory OR Use cases directory OR Prototypes directory presentInfra plans directory OR Infra specs directory present<Vision directory>/product-concept.md exists<Infra plans directory> has any subdirectories, OR if Dockerfile or docker-compose.yml exists in the project root{ plugin_name, has_activity: bool } for each detected plugin.CLAUDE.md file.## Arness section.## Arness section, extract core fields:
.arness/plans/).arness/specs/).arness/docs/)If ## Arness is missing: Skip to Step 3 and render the core pipeline diagram with all stages unmarked. Suggest the user run /arn-planning to get started for an existing project, or /arn-brainstorming for a brand-new project (requires arn-spark). Do not attempt detection.
Read the pipeline reference file at ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-help/references/pipeline-map.md to load detection rules, context-aware rendering rules, and next-step tables.
For each subdirectory in the plans directory, check artifacts to determine the most advanced stage. Check from most advanced to least advanced -- first match wins:
docs): A file matching the project name exists in the configured docs directory (<docs-dir>/<project>.md or <docs-dir>/<project>/ directory)execute-done): The subdirectory has PROGRESS_TRACKER.json with overallStatus = "completed". Note: arn-code-review-implementation does not write a durable artifact, so both "execution complete" and "review complete" map to this detection. The next-step suggestion covers both cases.execute): The subdirectory has any reports/IMPLEMENTATION_REPORT_*.json or reports/TESTING_REPORT_*.jsontaskify): The subdirectory has TASKS.md with parseable task entriessave): The subdirectory has INTRODUCTION.mdIf no per-project stages were detected:
SWIFT_* containing SWIFT_REPORT.json -- if found, stage is Swift complete (swift-complete)SWIFT_* containing SWIFT_*.md but no SWIFT_REPORT.json -- if found, stage is Swift in progress (swift-in-progress)STANDARD_* containing STANDARD_REPORT.json -- if found, stage is Standard complete (standard-complete)STANDARD_* containing STANDARD_*.md but no STANDARD_REPORT.json -- if found, stage is Standard in progress (standard-in-progress)PLAN_PREVIEW_*.md -- if found, stage is Plan generated (plan)FEATURE_*.md or BUGFIX_*.md -- if found, stage is Spec written (spec)DRAFT_FEATURE_*.md -- if found and no finalized FEATURE_*.md or BUGFIX_*.md exists, stage is Spec in progress (spec-draft)## Arness exists with core fields but specs and plans directories are empty, stage is Initialized (init). Suggest /arn-code-feature-spec, /arn-code-bug-spec, for quick changes (1-8 files) /arn-code-swift, or for medium complexity /arn-code-standard## Arness exists but no artifacts are found, stage is init.Read the pipeline templates and rendering rules from ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-help/references/pipeline-map.md.
Show the core pipeline diagram with the position marker. Follow the existing rendering:
After rendering the core pipeline status and next-step suggestion, append cross-plugin hints from Step 0:
/arn-spark-help for details."/arn-infra-help for details."init): show own suggestions FIRST (e.g., "Run /arn-code-feature-spec to spec a feature, /arn-code-bug-spec for a bug, /arn-code-swift for a quick fix, or /arn-code-assess for a codebase review"), then optionally mention other plugins./arn-planning". If Infra is configured: "Deploy with /arn-infra-wizard."Keep output concise -- the user wants a quick status check, not a wall of text. Show the diagram, the detected stage, the next command, and any cross-plugin hints. That is all.
After presenting the pipeline status:
${CLAUDE_PLUGIN_ROOT}/skills/arn-code-help/references/pipeline-map.md for answers -- do not re-scan the filesystem unless the user explicitly asks to refresh the detection.Arness-sketch detection: If a arness-sketches/ directory exists in the project root, note it in the status output: "Active sketches: arness-sketches/ directory detected with [N] route(s)." This is informational -- it does not affect pipeline position.
Common questions the user might ask:
/arn-planning which handles scope assessment and routes to the right workflow/arn-planning → /arn-implementing → /arn-shipping. Each entry point offers to chain to the next at completion./arn-planning, /arn-implementing, /arn-shipping, /arn-reviewing-pr, /arn-assessing/arn-spark-help for Spark exploration pipeline status."/arn-infra-help for Arness Infra pipeline status."/arn-code-assess for a guided technical review with prioritized improvements/arn-code-simplify after executing your plan or swift implementation. It auto-detects the scope from your most recent execution artifacts.## Arness section not found in CLAUDE.md -- Show the core pipeline diagram with no stage marked. Display "Not configured" as the current position. Suggest running /arn-planning for existing projects, or /arn-brainstorming for a brand-new project (requires arn-spark).init) stage for core. Suggest running /arn-code-feature-spec or /arn-code-bug-spec to create a specification (or /arn-code-feature-spec-teams for team debate format). For quick changes (1-8 files), suggest /arn-code-swift.init) stage for core. Suggest running /arn-code-feature-spec or /arn-code-bug-spec. For quick changes (1-8 files), suggest /arn-code-swift.spec stage. Otherwise mark init.## Arness not found. Show core pipeline unmarked and suggest /arn-planning or /arn-brainstorming./arn-code-init, /arn-code-plan, /arn-spark-discover). Do not use the fully qualified plugin:skill format in user-facing text.npx claudepluginhub appsvortex/arness --plugin arn-codeDetects current position in Arness Spark exploration pipeline, renders diagram with active stage marked, suggests next command. Provides cross-plugin awareness for Arness Code and Infra activity.
Initializes, configures, reviews, and upgrades Arness settings in CLAUDE.md for existing or new projects. Analyzes code patterns or recommends based on detected technologies.
Shows current position in Arness Infra workflow with ASCII diagram of pipeline stages, detects Quick or Full mode, and suggests next command. Read-only.