overview

Generate a consolidated project-overview.md from project-plan.md and build-plan.md planning documents.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill overview-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: overview
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/overview
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill overview-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping an AI assistant aligned with a project requires a single source of truth, but raw planning docs are often scattered, contradictory, or incomplete. This Skill validates two planning documents and distills them into one project overview that the AI loads every session. ## Core Features & Use Cases - Plan Validation: Checks that build-plan.md is a trackable numbered checkbox list of feature-sized outcomes, and flags vague, bundled, or placeholder items before generation. - Overview Synthesis: Merges project-plan.md and build-plan.md into blueprint/context/project-overview.md with concrete data models, ordered features, tech stack, and deployment constraints. - Conflict Surfacing: Reports contradictions and gaps between the two plans instead of silently reconciling them, and normalizes stub build plans only with user approval. - Use Case: After drafting a project plan and build checklist for a new SaaS app, run the Skill to produce the AI-facing overview doc, catch a missing feature in the checklist, and lock the data model before building features one at a time. ## Quick Start Run /overview to validate my blueprint/project-plan.md and blueprint/build-plan.md and generate the project overview document.

Frequently Asked Questions about overview

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

FAQPage Schema
How do I generate a project overview from planning documents?▼

Write blueprint/project-plan.md covering problem, users, features, data, and stack, plus blueprint/build-plan.md as a numbered checkbox feature list. Then run the overview skill, which validates both and writes blueprint/context/project-overview.md.

What format should a build plan checklist use for AI workflows?▼

Use a numbered checkbox list with '- [ ]' or '- [x]' items, one feature-sized outcome per line, ordered from first useful slice to later integrations. Avoid vague items like 'auth stuff' or pre-build setup chores like scaffolding.

What happens if my build plan is still a template stub?▼

The skill stops instead of generating over the gap. It derives the real checklist from project-plan.md's feature list, shows the reconciled version, and writes it into build-plan.md only after your approval.

Does the overview skill modify my planning documents automatically?▼

No, plans are user-owned. The skill proposes normalized plan text and stops for approval unless you explicitly asked it to clean up the plans in the same request. It never silently rewrites project-plan.md or build-plan.md.

When should I regenerate the project overview?▼

Re-run whenever project-plan.md or build-plan.md changes materially, such as a new feature, changed data model, or different stack. The overview is a generated artifact and should be regenerated rather than hand-edited.