phase1-mvp

Executes and verifies Phase 1 MVP closure for the Viru Air flight-tracking platform.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/javiruu/viru-air --skill phase1-mvp-javiruu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase1-mvp
Source: https://github.com/javiruu/viru-air/tree/main/skills/phase1-mvp
Command: npx skills add https://github.com/javiruu/viru-air --skill phase1-mvp-javiruu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing out a project phase requires verifying that every feature matches its specification, that backend and frontend contracts align, and that tests actually pass. This Skill provides a structured workflow to execute and verify Phase 1 MVP closure in the Viru Air repository, covering auth, quick search, watchlist, price history, alerts, and preferences with documented QA evidence. ## Core Features & Use Cases - Contract Alignment Validation: Cross-checks the quick-search contract between backend endpoints, frontend request builders, and canonical reference docs. - Operational Core Verification: Validates auth, watchlist, prices, alerts, and preferences API modules against the Phase 1 specification. - Targeted QA Evidence: Runs the target tests defined in the Phase 1 spec and reports exact command outputs with unresolved gaps. - Use Case: A developer needs to close Phase 1 of Viru Air before release. The Skill reads the canonical docs, validates each module against the spec, runs the defined test suite, and produces an evidence report with any contract mismatches and blockers. ## Quick Start Ask the assistant to execute and verify Phase 1 MVP closure for Viru Air using the canonical docs and report test evidence with any contract mismatches.

Frequently Asked Questions about phase1-mvp

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

FAQPage Schema
How do I verify an MVP phase is complete before release?▼

Verify MVP completion by aligning the scope with canonical specification docs, validating each feature module against the spec, running the target test suite, and documenting pass/fail evidence with concrete blockers for any failures.

How to check backend and frontend API contract alignment?▼

Compare the frontend request builder against the backend API endpoint and the written contract reference. For Viru Air, this means checking buildQuickSearchRequest.ts against backend/app/api/v1/search.py and the quick-search contract doc.

What does the Phase 1 MVP scope include in Viru Air?▼

Phase 1 covers authentication, quick search, watchlist, price refresh and history, alerts, and user preferences. The scope is defined in docs/specs/phase1-codex.md and must not expand into post-Phase-1 feature flags.

Can this workflow be used for features beyond Phase 1?▼

No, the Skill explicitly constrains work to the Phase 1 Definition of Done and forbids expanding scope to post-Phase-1 flags. Changes must stay surgical and tied to the documented Phase 1 spec.

What happens when target tests fail during phase verification?▼

Failures are documented with exact test command outputs and concrete blockers rather than being silently fixed or ignored. Any contract-risk mismatch is reported with specific file references for traceability.