shamt-lite-story

Execute a six-phase story workflow for ticket-based work in Shamt Lite.

Updated Feb 23, 2026

Search Tags:#planning #build #code-review #story-workflow #ticket-based #shamt-lite #spec-protocol

Ready to run

npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-lite-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: shamt-lite-story
Source: https://github.com/MizunoPK/shamt-ai-dev/tree/main/.claude/skills/shamt-lite-story
Command: npx skills add https://github.com/MizunoPK/shamt-ai-dev --skill shamt-lite-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines and standardizes the six-phase ticket-driven development workflow for teams using Shamt Lite, enabling consistent governance from intake to polish without relying on the full epic framework.

Core Features & Use Cases

Encodes the 5 core quality patterns: Validation Loops, Severity Classification, Spec Protocol, Code Review, and Implementation Planning.
Provides a complete six-phase lifecycle: Intake → Spec → Plan → Build → Review → Polish for ticket-based work.
Designed for projects that prefer structured, repeatable workflows with lightweight governance.

Quick Start

Tell the system to start a six-phase story for a ticket using a natural language command.

Frequently Asked Questions about shamt-lite-story

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

FAQPage Schema

What is a ticket-based story workflow for software development?▼

A ticket-based story workflow structures development into sequential phases from intake to polish, enforcing validation, specification, and code review to standardize governance for discrete units of work.

How do I manage code review and implementation planning for a development ticket?▼

You manage ticket code review and implementation planning by executing a six-phase lifecycle that applies validation loops and severity classification to gate decisions and structure build artifacts.

Does the Shamt Lite workflow require the full epic framework to manage stories?▼

No, the Shamt Lite workflow applies a lightweight deterministic six-phase story process and core quality patterns to guide execution without relying on the full epic framework.

What is the best way to enforce spec protocol and token discipline during ticket execution?▼

The best way to enforce spec protocol and token discipline is using a predefined template set that structures artifacts and gates decisions across the six story phases.

Can I use this six-phase story workflow for non-ticket-based development tasks?▼

No, this workflow requires a ticket-like input to trigger the six-phase lifecycle and apply quality patterns, making it unsuitable for unstructured or non-ticket-based development tasks.