dialogue-resolution

Detect specification-implementation discrepancies through a guided four-step approval workflow.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/amijadoamijado/sd003 --skill dialogue-resolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dialogue-resolution
Source: https://github.com/amijadoamijado/sd003/tree/main/.gemini/skills/dialogue-resolution
Command: npx skills add https://github.com/amijadoamijado/sd003 --skill dialogue-resolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

仕様と実装の差異を対話を通じて段階的に検出・可視化し、開発の安定性を高める手法です。

Core Features & Use Cases

  • 対話型差異検出: 仕様と実装の乖離を順序立てて報告します
  • 段階的検証フロー: Step 1〜Step 4 の実行と承認をガイドします
  • 適用ケース: 統合テストやプロンプト検証フェーズで有効です

Quick Start

Trigger dialogue-resolution to start the four-step diagnostic flow with the current proposal.

Frequently Asked Questions about dialogue-resolution

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

FAQPage Schema
How do I detect discrepancies between specifications and implementation in AI-assisted tasks?

Spec validation detects divergences in AI reasoning by applying a guided, stepwise evaluation flow that logs diffs and requires explicit approvals after each diagnostic step, ensuring prompt alignment during troubleshooting.

What is the best way to validate prompt alignment during integration and QA?

Prompt alignment during QA is best handled through dialogue-based diff reporting that sequentially compares specifications against implementation, guiding you through a four-step diagnostic flow with explicit approvals.

How does dialogue-based specification verification work for AI debugging?

Dialogue-based specification verification works by triggering a four-step diagnostic flow that sequentially reports divergences between your proposal and the implementation, logging diffs and planning fixes after explicit approvals.

Can I use dialogue-resolution for prompt engineering troubleshooting?

Yes, you can use dialogue-resolution for prompt engineering troubleshooting, as it applies to workflows involving prompt alignment, spec validation, and detecting discrepancies during integration and QA phases.

Does the stepwise diff reporting flow require external dependencies?

No external dependencies are required to run the stepwise diff reporting flow, allowing you to directly trigger the diagnostic process to evaluate specifications against implementations without additional environment setup.