audit
Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from…
Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
$ npx -y skills add suboss87/FDEOps --skill test-assumptions --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/test-assumptionsContext preview
The summary Claude sees to decide when to auto-load this skill.
Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
name: test-assumptions description: Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.
Before investigating or acting: 1. Read [the task context contract](references/task-context.md). 2. Read [the method](references/test-assumptions.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Skills for forward deployed engineers, used through your AI coding agent. FDEOps helps you turn a customer problem into a working system: clarify the goal, choose an architecture, build and integrate, then verify the result and prepare for rollout.
Repo: suboss87/FDEOps
Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from…
Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.
Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.
Implement a scoped software change for a customer and verify its behavior. Use for delivery work with an understood outcome, not incident response.
Develop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.
Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and…