arn-code-plan

Name: arn-code-plan
Availability: InStock
Author: AppsVortex

Generate an executable implementation plan from an Arness specification via the arn-code-feature-planner agent.

31|3|Updated Apr 3, 2026

Search Tags:#automation #planning #specification #plan-generation #arn-code-plan #PLAN_PREVIEW

Ready to run

npx skills add https://github.com/AppsVortex/arness --skill arn-code-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arn-code-plan
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-code/skills/arn-code-plan
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-code-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the translation of a formal Arness specification into a concrete, executable plan, reducing manual planning time and ensuring consistency across projects.

Core Features & Use Cases

Generates an implementation plan by invoking the arn-code-feature-planner agent.
Presents the PLAN_PREVIEW for user review and iterates on feedback until approval.
Outputs PLAN_PREVIEW to feed into arn-code-save-plan, linking planning to execution.

Quick Start

Initiate a plan for a specific spec by invoking arn-code-plan with your spec name.

Frequently Asked Questions about arn-code-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an implementation plan from a formal specification?▼

You can generate an implementation plan from a formal specification by invoking the planner with your spec name to automate translation into a concrete, executable plan, reducing manual planning time and ensuring consistency.

What is the best way to automate turning software specs into actionable tasks?▼

Automating software specs into actionable tasks is best handled by generating a preview artifact for user review and iterating on feedback until approval, ensuring the plan aligns with code changes before execution.

How does plan generation handle bug fixes alongside regular feature specs?▼

Plan generation for bug fixes and feature specs works by targeting planning tasks across both scopes, producing a preview artifact that links the planning process directly to necessary code changes for execution.

Do I need code-patterns documentation to generate an executable implementation plan?▼

You need access to the selected specification, and code-patterns documentation is required when available to inform the executable implementation plan and effectively link planning outputs to code changes.

Can I review the generated implementation plan before it gets executed?▼

You can review the generated implementation plan because the process presents a preview artifact for user review and iterates on your feedback until you grant final approval for staged execution.

How to integrate implementation planning with staged execution workflows?▼

To integrate implementation planning with staged execution, output the preview artifact to feed into a save-plan step, directly linking the approved planning phase to downstream code execution.