app-build-planner

Name: app-build-planner
Availability: InStock
Author: Stanford Spezi

Convert planning artifacts into a milestone-based implementation plan document.

22|5|Updated Nov 4, 2025

Search Tags:#automation #planning #documentation #milestones #software-development #project-management #implementation-plan

Ready to run

npx skills add https://github.com/StanfordSpezi/SpeziVibe --skill app-build-planner

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: app-build-planner
Source: https://github.com/StanfordSpezi/SpeziVibe/tree/main/skills/app-build-planner
Command: npx skills add https://github.com/StanfordSpezi/SpeziVibe --skill app-build-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered planning artifacts into a structured, milestone-based implementation plan that guides a coding agent from idea to delivery.

Core Features & Use Cases

Gather planning inputs from upstream skills and reference docs, extract the backlog of features, and define source-traceability for each item.
Map each feature to available packages or modules, identify gaps requiring custom implementation, and assign priorities (must-have, should-have, nice-to-have).
Sequence features into milestones using established milestone patterns, specify tasks, platform notes, verification criteria, and dependencies.
Produce a complete implementation plan document saved at the project root as docs/implementation-plan.md and ready for handoff to the coding agent.

Quick Start

Provide a complete implementation plan for the app build planner and save it as docs/implementation-plan.md.

Frequently Asked Questions about app-build-planner

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

FAQPage Schema

How do I convert planning artifacts into a milestone-based implementation plan?▼

To convert planning artifacts into a milestone-based implementation plan, you gather upstream planning outputs and reference docs, extract features, map them to packages, sequence them into milestones, and save the final plan as docs/implementation-plan.md.

What is the best way to sequence software development features into milestones for an automated coding agent?▼

Sequencing software development features into milestones for an automated coding agent involves extracting a feature backlog, mapping features to available packages, identifying custom implementation gaps, and assigning priorities like must-have or should-have before structuring the delivery sequence.

How do I map project features to existing packages and identify implementation gaps?▼

You map project features to existing packages by analyzing extracted features against available modules, identifying gaps requiring custom implementation, and assigning priorities such as must-have, should-have, or nice-to-have to guide development.

Do I need upstream planning outputs to generate an implementation plan?▼

Yes, upstream planning outputs, platform and backend decisions, and reference documents are required as starting inputs to extract the feature backlog and define source-traceability for the implementation plan.

What format does the generated implementation plan use for project handoff?▼

The generated implementation plan uses a markdown document format, specifically saved at the project root as docs/implementation-plan.md, ensuring it is ready for direct handoff to guide an automated coding agent.