autoplan

Chain three sprint planning commands into a single workflow using dragoon.json context.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Dragoon0x/dragoon-skills --skill autoplan-dragoon0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoplan
Source: https://github.com/Dragoon0x/dragoon-skills/tree/main/skills/autoplan
Command: npx skills add https://github.com/Dragoon0x/dragoon-skills --skill autoplan-dragoon0x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the need to run three separate planning commands sequentially to bootstrap a full sprint plan, cutting down setup time for new development initiatives and reducing repetitive manual work.

Core Features & Use Cases

  • Chained Planning Workflow: Combines the /brief, /plan-eng, and /plan-design commands into a single call to generate a complete sprint plan end-to-end.
  • Codebase-Aware Pre-Fills: All generated plan documents are pre-populated with facts from your project's dragoon.json manifest, so they align with your stack and project context automatically.
  • Flexible Execution Controls: Supports skipping individual planning steps you don't need, defaults to dry-run mode to preview outputs before writing files, and offers JSON output for tooling integration.
  • Use Case: When kicking off a new initiative like adding user authentication, use this Skill to generate all required planning documents in seconds instead of running three separate commands one after another.

Quick Start

Invoke the autoplan skill with your new feature idea to generate a complete set of sprint plan documents, and add the --apply flag if you want to save the generated files to your project.

Frequently Asked Questions about autoplan

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

FAQPage Schema
How do I generate a complete sprint plan in one command instead of running multiple planning steps?

To generate a complete sprint plan, use an automated planning workflow that chains brief, engineering, and design document generation into a single command. This eliminates running three separate planning steps sequentially, instantly pre-populating your initiative setup.

How do I pre-fill engineering and design plans with my project's tech stack automatically?

You can pre-fill engineering and design plans by pulling context from a dragoon.json manifest file. This codebase-aware approach automatically populates your generated sprint plan documents to match your specific stack and project facts.

Can I preview generated sprint planning documents before writing files to my project directory?

Yes, you can preview generated sprint planning documents using a default dry-run mode. This outputs plan previews without writing files, allowing low-risk execution before you commit to saving the brief, engineering, and design documents to your project.

What is the best way to skip unnecessary design or engineering planning steps during initiative setup?

The best way to skip unnecessary planning steps is to use selective step skipping controls within an automated planning workflow. This allows you to bypass specific design or engineering document generation, tailoring the sprint plan output to your immediate needs.

Do I need a dragoon.json manifest to generate codebase-aware sprint plans?

Yes, a dragoon.json manifest is required to generate codebase-aware sprint plans. The automated planning workflow reads this manifest to pre-populate your brief, engineering, and design documents with accurate stack and project context.

How do I save generated initiative planning files to a specific directory?

To save generated initiative planning files, you apply an execution flag after previewing the output. This writes the generated brief, engineering, and design plan documents directly to the .dragoon/plans directory in your project.