resolve-contract-gaps

Resolve contradictory contract and policy gaps into one canonical decision set persisted in DECISIONS.md.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill resolve-contract-gaps-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-contract-gaps
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/resolve-contract-gaps
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill resolve-contract-gaps-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering tasks often stall because behavior, contract, or policy rules are ambiguous or contradictory, and planning cannot proceed safely until one canonical rule set exists. This Skill turns those unresolved gaps into explicit, reviewable decision proposals recorded in DECISIONS.md and TASK_STATE.md instead of silent intent changes. ## Core Features & Use Cases - Gap Resolution: For each unresolved issue, it explains the ambiguity, lists viable options with trade-offs, and recommends one canonical rule with exact implementation and test consequences. - Decision Tables: Produces input-condition-to-action decision tables when multiple entwined issues exist, reducing downstream interpretation risk. - Governed Persistence: Writes semantic changes to DECISIONS.md only as PROPOSED unless explicitly approved, and emits no-op traces when artifacts would not materially change. - Use Case: During a feature build, two modules disagree on which field owns the source of truth. Run this Skill to compare options, recommend one rule, and record the proposal for sign-off before planning continues. ## Quick Start Resolve the outstanding contract ambiguities in my active task and propose canonical decisions in DECISIONS.md.

Frequently Asked Questions about resolve-contract-gaps

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

FAQPage Schema
How do I resolve contradictory contract rules before planning a feature?▼

Run this Skill on the active task folder. It reads TASK_STATE.md, SOURCE_OF_TRUTH.md, and DECISIONS.md, then lists each ambiguity with viable options, trade-offs, and one recommended canonical rule including exact implementation and test consequences.

When should I use resolve-contract-gaps instead of decision-interview?▼

Use it when ambiguities are already identified and enough facts exist to compare options safely. If basic factual context is missing or decision questions remain unanswered, run decision-interview first, then return here to establish the canonical rule set.

Does this Skill write decisions to DECISIONS.md automatically?▼

No. Semantic changes to DECISIONS.md are marked PROPOSED unless the user explicitly approves them in chat or they are already authoritative. Only non-semantic editorial hardening that does not change meaning can be applied directly.

What happens if the contract gaps are already resolved?▼

The Skill returns a no-op instead of rewriting DECISIONS.md or churning TASK_STATE.md. It emits a short NO_OP trace note for auditability and routes forward to the appropriate next command.

When is a decision table produced in the output?▼

A decision table mapping input conditions to actions and runtime or data effects is produced when two or more entwined issues exist or input variations affect behavior. Otherwise the output explicitly states why a table is not useful for that issue set.