octocode-plan

Orchestrate research-driven planning to produce a plan.md with references.

904|77|Updated Jun 5, 2025
One-click install
npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: octocode-plan
Source: https://github.com/bgauryy/octocode-mcp/tree/main/packages/octocode-cli/skills/octocode-plan
Command: npx skills add https://github.com/bgauryy/octocode-mcp --skill octocode-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates research-driven planning to convert findings into actionable implementation plans.

Core Features & Use Cases

  • Phase-driven workflow: Understand → Research → Plan → Implement → Verify with explicit approval gates.
  • Research delegation: Automatically allocate local and external research tasks to specialized skills (e.g., octocode-local-search, octocode-research) and consolidate results.
  • Evidence-backed planning: Produce a traceable plan.md that references research findings, with clear dependencies and risk flags.
  • Multi-repo support: Coordinate planning across single or multiple repositories with versioned session contexts.
  • Use Case: When planning a feature across modules, generate a step-by-step plan, identify tasks, and capture decisions before coding.

Quick Start

Start a planning session named "feature-x-plan" and let the agent collect context, discover research findings, and generate a detailed plan.md with approved steps.

Frequently Asked Questions about octocode-plan

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

FAQPage Schema
How do I convert software research findings into an actionable implementation plan?

Software research findings are converted into actionable implementation plans by orchestrating research-driven planning that produces a traceable plan.md with clear dependencies, risk flags, and references to the original research.

What is evidence-based planning for multi-repo software projects?

Evidence-based planning for multi-repo software projects coordinates local and external research tasks across single or multiple repositories, producing versioned session contexts and a plan.md that references consolidated research findings.

How do I coordinate AI agents for research tasks before coding a feature?

AI agents are coordinated for research tasks through a phase-driven workflow that automatically allocates local and external research to specialized skills, consolidating results before generating an approved step-by-step implementation plan.

Can I enforce explicit approval gates between planning and implementation phases?

Explicit approval gates are enforced between the Understand, Research, Plan, Implement, and Verify phases, ensuring phase-driven workflow requires explicit approvals before execution of any implementation step begins.

Does phase-driven planning support traceability for software engineering decisions?

Phase-driven planning supports traceability by producing an evidence-backed plan.md that explicitly references research findings, capturing decisions with clear dependencies and risk flags before any coding starts.

What's the best way to plan a feature across multiple software modules?

Planning a feature across multiple software modules is best handled by starting a named planning session that collects context, discovers research findings via delegated tasks, and generates a detailed plan.md with approved steps and multi-repo coordination.