gameplan

Generate engineering gameplans with milestones and acceptance criteria from PRDs and architecture proposals.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/dpaola2/pipeline-skills --skill gameplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gameplan
Source: https://github.com/dpaola2/pipeline-skills/tree/main/.claude/skills/gameplan
Command: npx skills add https://github.com/dpaola2/pipeline-skills --skill gameplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms approved architecture and product requirements into a detailed, actionable engineering gameplan, ensuring clarity and alignment before development begins.

Core Features & Use Cases

  • Milestone Breakdown: Organizes work into logical, feature-based milestones with clear deliverables.
  • Acceptance Criteria Generation: Defines specific, testable criteria for each milestone.
  • Non-Functional Requirements: Ensures critical aspects like security, performance, and testing are addressed.
  • Use Case: After an architecture is approved for a new feature, use this Skill to generate a step-by-step engineering plan, including tasks, dependencies, and acceptance criteria, ready for the development team.

Quick Start

Use the gameplan skill to generate an engineering gameplan for the project identified by 'SN-3'.

Frequently Asked Questions about gameplan

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

FAQPage Schema
How do I generate an engineering gameplan from approved architecture proposals?

Engineering gameplans require synthesizing your PRD, discovery reports, and approved architecture proposals. This process breaks down projects into functional milestones, defines specific acceptance criteria, maps platform tasks, and addresses non-functional requirements like security and performance.

What is the best way to break down a software project into milestones with acceptance criteria?

Breaking down a software project involves organizing work into logical, feature-based milestones with clear deliverables. You then define specific, testable acceptance criteria for each milestone while mapping platform tasks and addressing non-functional requirements.

Do I need a finalized PRD and architecture proposal before creating a project plan?

Yes, you need a finalized PRD and approved architecture proposal before creating a project plan. The gameplan generation process synthesizes these specific inputs, along with discovery reports, to transform approved product requirements into an actionable engineering plan.

How are non-functional requirements like security and performance handled during project planning?

Non-functional requirements like security, performance, and testing are handled by explicitly addressing them during the gameplan generation. This ensures critical technical aspects are integrated into the functional milestones and acceptance criteria before development begins.

Can I use this approach to map platform tasks and dependencies for my engineering team?

Yes, you can use this approach to map platform tasks and dependencies for your engineering team. It generates a step-by-step engineering plan from your architecture proposals, ensuring coherence and traceability across all mapped tasks before your development team starts implementation.