skills.rest
calcosmic
calcosmicCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

planning-assumption-audit

Identify hidden planning assumptions and document them in ASSUMPTIONS.md.

9|1|Updated Feb 1, 2026
Search Tags:#workflow#planning#documentation#assumptions#decision-making#stakeholders#risk-identification
One-click install
npx skills add https://github.com/calcosmic/Aether --skill planning-assumption-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-assumption-audit
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/colony/planning-assumption-audit
Command: npx skills add https://github.com/calcosmic/Aether --skill planning-assumption-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface the invisible decisions hiding inside an approach before they become expensive mistakes. When someone describes what to build, they're also implicitly deciding how to build it -- technology choices, scope boundaries, priority orderings, and user model assumptions they may not realize they're making. This skill drags those assumptions into the light so they can be confirmed, corrected, or consciously accepted.

Core Features & Use Cases

  • Surface hidden assumptions early to prevent costly rework in planning.
  • Categorize assumptions by risk and impact to guide decision-making.
  • Document an actionable plan (ASSUMPTIONS.md) that stakeholders can review.

Quick Start

Schedule a pre-planning session to surface implicit decisions and generate an ASSUMPTIONS.md.

Frequently Asked Questions about planning-assumption-audit

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

FAQPage Schema
How do I identify hidden planning assumptions before project execution?▼

Identifying hidden planning assumptions requires a structured pre-planning workflow to surface, categorize, and document unstated constraints and decisions based on risk and impact. This prevents costly rework by exposing implicit choices early.

What is the best way to document unstated constraints for stakeholder review?▼

The best way to document unstated constraints is to generate an actionable ASSUMPTIONS.md file during a pre-planning session. This allows stakeholders to review, confirm, correct, or consciously accept the implicit decisions hiding inside an approach.

Why does implicit decision-making cause costly rework in product and architecture planning?▼

Implicit decision-making causes costly rework because unstated assumptions regarding technology choices, scope boundaries, and user models remain unchallenged. Surfacing these hidden assumptions early prevents expensive wrong turns during execution.

Can I use this assumption audit workflow for early phase process design?▼

Yes, you can use this workflow for early phase process design. It is specifically applicable across product, architecture, and process design to surface hidden assumptions and enforce risk-based prioritization before you act.

How do I categorize planning assumptions by risk and impact for decision-making?▼

You categorize planning assumptions by risk and impact by enforcing a structured workflow that surfaces unstated constraints and documents them with risk-based prioritization. This guides stakeholders in confirming or correcting critical decisions.

Related Skills

Explore More Product & Management Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
rikdcrikdc
2

specify

Converts design documents into technical specifications with data models and API contracts.

Community
Basic
vanman2024vanman2024
3

code-generation

Detect project frameworks and generate framework-aligned code templates.

Community
Intermediate
Patasse97Patasse97

product-discovery

Validate product opportunities using OST mapping and structured discovery workflows.

Community
Intermediate