create-assumption

Document implementation assumptions with context, risk, and validation plans.

5|Updated Jul 25, 2025

Search Tags:#documentation #validation #assumptions #sdlc #risk-management #record-keeping

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-assumption

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-assumption
Source: https://github.com/tomzx/agents/tree/main/skills/create-assumption
Command: npx skills add https://github.com/tomzx/agents --skill create-assumption

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Records an assumption made during implementation: what is being assumed, why, how confident the team is, what breaks if the assumption turns out to be false, and how to validate it.

Core Features & Use Cases

Capture and document the assumption with context, basis, risk, and validation plan.
Save the assumption in a standardized location (.sdlc/knowledge/assumptions/) using a deterministic filename pattern.

Quick Start

Save the assumption to the next available numeric prefix under .sdlc/knowledge/assumptions following the NNNN-<slug>.md format.

Frequently Asked Questions about create-assumption

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

FAQPage Schema

How do I document implementation assumptions for risk management?▼

To document implementation assumptions, you record the context, evidence, potential impact, confidence level, and a validation plan. This captures what breaks if the assumption is false and outlines steps to validate or refute it.

What is the best way to track software design assumptions during the SDLC?▼

Tracking software design assumptions involves saving them in a standardized location like .sdlc/knowledge/assumptions/ using a deterministic filename pattern. This ensures assumptions are recorded systematically with their basis and validation plans.

How do I validate assumptions made during software delivery?▼

Validating software delivery assumptions requires defining a specific plan to test or refute them when documenting. You capture the assumption's basis and confidence level, then outline actionable steps to verify its accuracy before it impacts the system.

Does this assumption recording process require any specific dependencies?▼

No specific dependencies are required to record implementation assumptions. You only need a file system to save the assumption markdown files into the .sdlc/knowledge/assumptions/ directory using the NNNN-<slug>.md naming pattern.

When do I need to record an assumption in the SDLC knowledge base?▼

You need to record an assumption in the SDLC knowledge base whenever an implementation decision is made based on an unverified premise that could impact design, delivery, or risk, ensuring the team has a plan to validate it.