sm:shape:gate

Runs a five-question readiness check for shaped work before staging.

5|2|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/mnfst-ai/Stage_Manager_Skills --skill sm-shape-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sm:shape:gate
Source: https://github.com/mnfst-ai/Stage_Manager_Skills/tree/main/plugins/stage-manager/skills/shape-to-stage-gate
Command: npx skills add https://github.com/mnfst-ai/Stage_Manager_Skills --skill sm-shape-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly missteps at the boundary between shaping and staging by surface-checking readiness, naming load-bearing assumptions, and catching holes a coding tool might otherwise invent its own solutions for. It balances speed and rigor so builders don't stage too soon or get stuck over-shaping, saving hours and reducing downstream technical debt.

Core Features & Use Cases

  • Five focused questions that run in sequence, stopping immediately when a real finding arises to prioritize action over ceremony.
  • Clear verdicts and routing: returns Ready, Almost, or Not Yet and recommends the specific upstream skill or quick fix needed.
  • Terminal-friendly output: formats the conversation and verdict for scanability and direct use with Claude Code or other agentic tools.
  • Use case: A vibe coder about to hand a new feature to an automated coding agent runs the gate to ensure the user outcome, riskiest assumption, holes, soul alignment, and first chunk are explicit before prompts are written.

Quick Start

Run the Shape-to-Stage Gate and walk me through the five readiness questions before I write the first prompt.

Frequently Asked Questions about sm:shape:gate

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

FAQPage Schema
How do I check if a feature is ready for staging before writing coding prompts?

A stage-gate readiness check validates assumptions, identifies open holes, and ensures your user outcome, soul alignment, and first chunk are explicit before handing tasks to coding tools.

What is a stage-gate validation check for vibe coding?

It applies at the boundary between shaping and staging, producing a terminal-friendly analysis that prevents coding tools from inventing their own solutions for missing details.

How do I chunk work before handing tasks to an automated coding agent?

This prevents staging too soon or getting stuck over-shaping, reducing downstream technical debt by catching holes a coding tool might otherwise fill with its own assumptions.

Can I use a readiness gate with Claude Code or other agentic coding tools?

It outputs a one-line Ready, Almost, or Not Yet verdict and routes you to the specific upstream skill or quick fix needed if work is not yet ready for staging.

When should I not use a stage-gate readiness check?

If no real findings arise during the five questions, the check prioritizes action over ceremony and may simply confirm readiness rather than adding heavy validation overhead.