plan

Analyze modular-dev tasks to identify affected graph nodes before implementation.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Arrosam/Modular-Dev --skill plan-arrosam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Arrosam/Modular-Dev/tree/main/skills/plan
Command: npx skills add https://github.com/Arrosam/Modular-Dev --skill plan-arrosam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you figure out what parts of a modular-dev project need to change before any code is written, so large tasks can be broken into clear, manageable work.

Core Features & Use Cases

  • Dependency-Aware Analysis: Reads the project graph and related overviews to determine which nodes, contracts, and zones are affected.
  • Zone Routing: Directs the task to the right zone managers so each impacted area can be analyzed in context.
  • Implementation-Ready Specs: Produces detailed, BFS-ordered development plans with files, methods, data flow, and cross-zone impact notes.
  • Use Case: Use this Skill when you need to understand the full change surface for a feature request, bug fix, or refactor before development begins.

Quick Start

Ask the plan skill to analyze your modular-dev task and tell you which nodes, contracts, and zones need to change before implementation starts.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan modular development changes before writing code?

To plan modular development changes, you analyze the project graph and contract overviews to determine which nodes, contracts, and zones are affected before implementation begins.

What is BFS-based dependency graph planning for software engineering?

BFS-based dependency graph planning traverses project nodes breadth-first to identify the full change surface, producing ordered development specs with files, methods, and cross-zone impact notes.

How do I route a feature request to the correct zone managers?

You route a feature request to the correct zone managers by analyzing the dependency graph to detect which specific contracts and zones are impacted by the proposed modular changes.

Can I use this for bug fixes and refactoring tasks, not just new features?

Yes, you can use this for bug fixes and refactoring tasks. The analysis applies to any change description, identifying affected nodes and generating implementation-ready development specs.

What is the best way to detect contract impacts across modular project zones?

The best way to detect contract impacts is reading the project graph and related overviews to map dependencies, ensuring each impacted zone is analyzed in context by its respective managers.