list-phase-assumptions

Surface Copilot's phase assumptions across five planning areas with interactive corrections.

17|4|Updated Oct 8, 2021
One-click install
npx skills add https://github.com/virtengine/virtengine --skill list-phase-assumptions-virtengine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: list-phase-assumptions
Source: https://github.com/virtengine/virtengine/tree/main/.github/skills/list-phase-assumptions
Command: npx skills add https://github.com/virtengine/virtengine --skill list-phase-assumptions-virtengine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface Copilot's assumptions about a phase before planning are surfaced. It helps teams correct misconceptions early and align on expectations.

Core Features & Use Cases

  • Structured assumption surface across five areas: Technical Approach, Implementation Order, Scope Boundaries, Risk Areas, Dependencies.
  • Interactive feedback loop to capture corrections and replan.
  • Lightweight, auditable workflow that can be repeated for other phases.

Quick Start

Run /list-phase-assumptions.md 3 to surface assumptions for Phase 3.

Frequently Asked Questions about list-phase-assumptions

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

FAQPage Schema
How do I surface assumptions before planning a product phase?

Surfacing phase assumptions involves exposing technical approach, implementation order, scope boundaries, risk areas, and dependencies for interactive review and correction before planning begins.

Why clarify phase assumptions during the planning stage?

Clarifying phase assumptions during planning helps teams correct misconceptions early and align on expectations before implementation, reducing downstream rework and scope creep.

What is the best way to correct incorrect assumptions in a product roadmap?

The best way to correct assumptions in a product roadmap is through an interactive feedback loop that captures corrections directly against surfaced assumptions and triggers replanning for traceability.

Does assumption surfacing work for repeating phases in a roadmap?

Yes, assumption surfacing works for repeating phases because it uses a lightweight, auditable workflow that can be repeated and applied independently to subsequent phases in a roadmap.

How do I review technical approach and scope boundaries for a phase?

Review technical approach and scope boundaries by running a structured assumption surface command for the target phase, which outputs these areas alongside implementation order, risks, and dependencies for interactive correction.