eng-plan

Generate structured multi-document implementation plans with gate-based milestones.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-plan
Source: https://github.com/viditparashar96/second-brain-claude/tree/main/skills/eng-plan
Command: npx skills add https://github.com/viditparashar96/second-brain-claude --skill eng-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex initiatives is error-prone when done ad-hoc. The Implementation Planner automatically creates a dedicated task folder with four documentation artifacts to standardize scope, progress tracking, decisions, and implementation notes.

Core Features & Use Cases

  • Generates a consistent task scaffold under docs/plans/{task-name} including plan.md, status.md, decisions.md, and implementation-notes.md.
  • Supports gating via Phase 0 Spike and subsequent phases with explicit gates, ownership, and acceptance criteria.
  • Applies selective expert analysis to tailor the planning process for product, engineering, and project-management contexts.

Quick Start

Describe the feature or task you want planned, and I will generate a structured task plan.

Frequently Asked Questions about eng-plan

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

FAQPage Schema
How do I create a structured project management plan for a complex engineering initiative?

Structured task planning for complex initiatives generates a dedicated folder containing plan, status, decisions, and implementation notes documents. This standardizes scope, tracks progress, and establishes clear ownership across phased gates.

What is gate-based milestone planning and when do I need it for product launches?

Gate-based milestone planning uses explicit acceptance criteria and ownership checkpoints between phases, starting with a Phase 0 Spike. You need it for product launches, engineering upgrades, and cross-functional projects requiring reliable delivery and clear decisions.

How do I track implementation decisions and project status separately during a software upgrade?

Implementation decisions and project status are tracked separately by generating distinct decisions.md and status.md artifacts within a task folder. This isolates architectural choices from progress tracking, ensuring reliable delivery documentation for software upgrades.

Can I use existing product context from PRODUCTS.md when generating a task plan?

Yes, the task planning process reads context from a PRODUCTS.md file when available. This allows the generated implementation plan, milestones, and gate criteria to align with existing product documentation and cross-functional project requirements.

What is the best way to document a Phase 0 Spike for an engineering upgrade?

The best way to document a Phase 0 Spike is using a structured plan.md scaffold that defines explicit gates, ownership, and acceptance criteria. This standardizes the initial research phase before committing to subsequent implementation phases.

What documentation artifacts are needed for reliable delivery in cross-functional projects?

Reliable delivery in cross-functional projects requires four documentation artifacts: plan.md for scope, status.md for progress, decisions.md for choices, and implementation-notes.md for technical context. These standardize task planning and gate-based milestones.