shamt-spec-protocol

Guide software spec creation through a 10-dimension validation loop.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-spec-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shamt-spec-protocol
Source: https://github.com/MizunoPK/shamt-ai-dev/tree/main/.claude/skills/shamt-spec-protocol
Command: npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-spec-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec creation and refinement for software epics and features often suffer from batching, scope creep, and unclear acceptance criteria. This Skill enforces a one-question-at-a-time interaction model and a structured 10-dimension validation loop to ensure traceability, alignment with epic scope, and readiness for mechanical planning.

Core Features & Use Cases

  • Critical Workflow Rules: ONE QUESTION AT A TIME; INVESTIGATION COMPLETE ≠ QUESTION RESOLVED; updates are applied immediately after each answer.
  • Spec Refinement Validation Loop: 10-dimension gate-based validation (D1–D7 master plus D8–D10 spec-specific) before user approval.
  • Gate-based Workflow: Embedded gates during the loop (Gate 1/2) and a final Gate 3 for user approval, ensuring cross-feature alignment and measurable acceptance criteria.

Quick Start

Initiate the spec refinement loop for a feature spec to begin the one-question-at-a-time workflow and validation gates.

Frequently Asked Questions about shamt-spec-protocol

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

FAQPage Schema
How do I enforce one-question-at-a-time during software spec refinement?

Spec refinement is enforced by a one-question-at-a-time interaction model that applies updates immediately after each answer, preventing batching and scope creep. This disciplined workflow ensures traceability and alignment before proceeding to validation.

What is a 10-dimension validation loop for epic planning?

A 10-dimension validation loop is a gate-based spec refinement process checking D1–D7 master dimensions and D8–D10 spec-specific criteria. It ensures cross-feature alignment and measurable acceptance criteria before final user approval.

How do I prevent scope creep when creating feature specifications?

Prevent scope creep in feature specifications by applying a structured validation loop with embedded gates. This enforces traceability and scope alignment, ensuring cross-feature consistency before user approval and mechanical planning.

Can I use gate-based workflows for S2 spec development?

Yes, gate-based workflows are applied to S2 spec development and epic documentation. The process uses Gate 1 and Gate 2 during the validation loop, concluding with Gate 3 for final user approval to yield production-ready specifications.

Best way to ensure traceability and acceptance criteria in software epics?

The best way to ensure traceability is through a structured 10-dimension validation loop for epic documentation. This gate-based workflow enforces formal acceptance criteria and cross-feature alignment, yielding production-ready specifications for planning.