blueprint

Maintain product blueprints documenting flows, entities, APIs, and system contracts.

1|Updated May 26, 2026

Search Tags:#architecture #documentation #api contracts #blueprint #product #flows

Ready to run

npx skills add https://github.com/virajp/ai-plugins --skill blueprint-virajp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/virajp/ai-plugins/tree/main/plugins/vwf/skills/blueprint
Command: npx skills add https://github.com/virajp/ai-plugins --skill blueprint-virajp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents product documentation drift by maintaining a complete, traceable blueprint of flows, entities, APIs, and system contracts before implementation planning begins.

Core Features & Use Cases

Flow-first blueprint authoring: Create and maintain product flow documents that connect goals, user journeys, entities, screens, jobs, and API operations.
Contract consistency management: Keep entity schemas, OpenAPI contracts, conventions, and architecture records synchronized with reviewed product decisions.
Whole-product coverage reviews: Run completeness checks and coherence reviews to identify missing flows, broken links, contract gaps, and blueprint inconsistencies before planning.

Quick Start

Use the blueprint skill to review and complete the product blueprint coverage for the current repository.

Frequently Asked Questions about blueprint

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

FAQPage Schema

How do I prevent product documentation drift before implementation planning?▼

Prevent product documentation drift by maintaining a complete, traceable blueprint of flows, entities, APIs, and system contracts. Run coherence reviews and coverage checks to identify missing flows, broken links, and contract gaps before implementation begins.

What is a flow-first product blueprint and how does it work?▼

A flow-first product blueprint connects goals, user journeys, entities, screens, jobs, and API operations into a single traceable document. It works by linking architectural decisions to product flows, ensuring requirements traceability and architecture alignment across all product surfaces.

How do I keep OpenAPI contracts synchronized with product decisions?▼

Keep OpenAPI contracts synchronized with product decisions through contract consistency management. This validates entity schemas, conventions, and architecture records against reviewed product decisions, ensuring API contracts remain aligned with the documented flows and entities.

Can I run completeness checks for missing flows and contract gaps in my repository?▼

Yes, you can run whole-product completeness checks and coherence reviews directly on your repository. These checks identify missing flows, broken links, contract gaps, and blueprint inconsistencies to ensure full documentation coverage before planning implementation.

What's the best way to maintain architecture alignment for product engineering workflows?▼

Maintain architecture alignment by documenting system contracts, entity schemas, and architecture records alongside product flows. This approach enforces requirements traceability and documentation governance, ensuring engineering implementation matches reviewed blueprint artifacts.

Do I need reviewed blueprint artifacts before validating system contracts?▼

Yes, contract validation requires reviewed blueprint artifacts as a baseline. The validation process checks coherence and structured coverage tracking across product surfaces, ensuring entity schemas and OpenAPI contracts align with approved product decisions before implementation planning.