spec

Convert requirements into a gated specification workflow with checkpoints and reviewers.

25|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/toongri/oh-my-toong-playground --skill spec-toongri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/toongri/oh-my-toong-playground/tree/main/skills/spec
Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill spec-toongri

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces the rigorous spec workflow Claude Code requires, turning informal requirements into a structured, user-gated specification that never skips checkpoints, areas, or documentation handoffs.

Core Features & Use Cases

  • Structured Expert Guidance: Provides design principles, question protocols, wrapup rules, and multi-agent review mandates so spec writers stay compliant with the Claude Code conventions.
  • Area-Specific Playbooks: Loads detailed processes for each design area (Requirements, Solution Design, Domain Model, etc.) plus emergent concern handling, ensuring no decision is left undocumented.
  • Use Case: Use this Skill when you need to convert a stakeholder conversation into a traceable spec with records, review feedback, and context files ready for future projects.

Quick Start

Tell the spec skill to transform the current requirements into a gated specification with area checkpoints and wrapup context.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I translate informal requirements into a structured architecture specification?

To create an architecture specification, you must transform informal stakeholder requirements into a gated workflow that enforces design checkpoints, area-specific reviews, and documentation handoffs. This ensures every architectural decision is captured and verified.

What is a gated specification workflow for AI-assisted projects?

A gated specification workflow is a structured process that enforces mandatory checkpoints and reviewer approvals between requirements gathering, solution design, domain modeling, and wrapup. It guarantees no architectural phase is skipped and produces verifiable artifacts.

How do I ensure architectural decisions are captured during the design workflow?

To capture architectural decisions, apply a questioning protocol and multi-agent review mandates throughout the design workflow. This enforces rigorous documentation of decision logic and produces context files for future AI-assisted projects.

Can I use a specification workflow to handle emergent concerns in solution design?

Yes, a disciplined specification workflow loads detailed processes for each design area and includes emergent concern handling. This ensures no unexpected design decision is left undocumented during the architectural review.

What is the best way to enforce multi-agent reviews for architectural specs?

The best way to enforce multi-agent reviews is to apply a structured specification workflow with mandated reviewer checkpoints and wrapup rules. This guarantees compliance with design conventions and produces traceable context files.