assumptions-managerlisted

# Assumptions Manager ## Purpose Track the assumptions the project is currently relying on and keep them visible as the project moves through the VDD journey. This skill exists to prevent invisible assumptions from becoming accidental requirements. ## When to Use Use this skill when: - a new assumption is discovered or confirmed - an existing assumption changes confidence or risk - a stage transition depends on an assumption remaining visible - an agent needs to preserve assumptions for downstream execution ## When Not to Use Do not use this skill when: - there are no meaningful assumptions to record - the task is only to inspect or resume context - the assumption has already been captured and does not need a state update ## Core Responsibilities This skill is responsible for: - recording assumptions clearly and concisely - assigning a visible status to each assumption - preserving owner, confidence, and risk when known - surfacing assumptions that block or weaken readiness - carrying assumptions forward across stages ## Assumption Statuses Use clear statuses such as: - `open` - `accepted` - `validated` - `reclassified` - `blocking` - `retired` ## Assumption Rules This skill should: - keep each assumption explicit and traceable - tie assumptions back to source context when available - separate validated facts from provisional beliefs - surface high-risk assumptions early - keep unresolved assumptions visible to downstream agents This skill should not: - hi