plan

Assess software project requirements, risks, and pipeline strategy without modifying files.

54|3|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/arcasilesgroup/ai-engineering --skill plan-arcasilesgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/arcasilesgroup/ai-engineering/tree/main/.agents/skills/plan
Command: npx skills add https://github.com/arcasilesgroup/ai-engineering --skill plan-arcasilesgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert guidance on project planning, requirement discovery, and risk assessment without making any changes to your codebase.

Core Features & Use Cases

  • Requirement Discovery: Analyzes project needs and gathers evidence from existing documentation and code.
  • Risk Assessment: Identifies and evaluates potential technical, security, and governance risks.
  • Pipeline Recommendation: Suggests an appropriate development pipeline strategy (full, standard, hotfix, trivial).
  • Use Case: Before starting a new feature, use this Skill to understand its scope, potential challenges, and the best way to approach development.

Quick Start

Ask the plan skill to assess the scope for adding OAuth support to the application.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I assess technical risks before starting a new software feature?

Risk assessment for software features involves discovering requirements, evaluating architecture, and identifying security or governance risks. This advisory process produces a planning document that classifies the pipeline strategy without modifying files.

Can I get advisory planning for software development without modifying my codebase?

Yes, read-only advisory planning provides requirement discovery and risk assessment without executing or modifying files. It classifies pipelines and produces a conversational planning document to guide your development strategy.

How do I analyze project requirements and gather evidence from existing code?

Requirement discovery analyzes project needs by gathering evidence from existing documentation and code. This process assesses potential technical, security, and governance risks to recommend an appropriate pipeline strategy.

When do I need a full pipeline strategy versus a hotfix pipeline?

Pipeline strategy classification recommends full, standard, hotfix, or trivial pipelines based on discovered requirements and risk assessments. This advisory evaluation helps determine the appropriate development approach for your software project.