plan-eng

Generate structured engineering plan markdown with codebase facts and mandatory checklists.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the tedious, error-prone work of manually drafting engineering plans that often miss critical guardrails like edge cases, test coverage, and migration steps, while ensuring every plan aligns with your codebase's actual tech stack and current design quality standards.

Core Features & Use Cases

  • Auto-Populated Context: Pulls stack, dependencies, and current critique scores directly from dragoon.json to eliminate manual data entry.
  • Enforced Structure: Mandates inclusion of 5+ edge cases, a full test matrix, migration/rollback plans, and a review checklist gated on your quality threshold.
  • Use Case: When planning a non-trivial feature like user authentication, this Skill generates a complete, standards-compliant engineering plan in seconds instead of hours of manual work.

Quick Start

Use the plan-eng skill to generate a structured, codebase-aligned engineering plan for your new feature idea.

Frequently Asked Questions about plan-eng

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

FAQPage Schema
How do I generate an engineering plan that includes edge cases and test matrices?

Generate a structured engineering plan by enforcing mandatory inclusion of 5+ edge cases, a full test matrix, and migration plans. This ensures pre-implementation planning covers critical guardrails aligned with your codebase context.

What is a pre-implementation engineering plan and when do I need one?

A pre-implementation engineering plan is a structured markdown document for non-trivial features exceeding single-file modifications. You need one after initial brief drafting to enforce design quality, edge case lists, and review checklists.

Can I auto-populate an engineering plan with my codebase stack and dependencies?

Yes, you can auto-populate engineering plans with codebase facts by pulling stack, dependencies, and current design critique scores directly from dragoon.json. This eliminates manual data entry and ensures stack alignment.

How do I add migration and rollout plans to my feature engineering plan?

Add migration and rollout plans by generating a structured engineering plan that mandates these sections. The plan enforces inclusion of migration steps, rollback plans, and review checklists gated on your codebase's quality threshold.

What's the best way to plan a non-trivial feature like user authentication?

The best way to plan a non-trivial feature is generating a standards-compliant engineering plan pre-populated with codebase context. This enforces edge case lists, test matrices, and review checklists instead of hours of manual drafting.