spec

Automate upstream requirements ceremonies for stories with skeleton creation and spec writing.

Updated Apr 7, 2026

Search Tags:#automation #workflow #spec-writing #upstream #gate-review #story-management #ceremony

Ready to run

npx skills add https://github.com/ramontramontini/CTEDemo --skill spec-ramontramontini

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/spec
Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill spec-ramontramontini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Upstream requirements ceremony coordinates end-to-end work for a story, including skeleton creation, epic context loading, exploration, spec writing, gateKeeper reviews, and downstream routing.

Core Features & Use Cases

End-to-end ceremony orchestration: skeleton creation, epic context loading, exploration, spec writing, gate reviews, and plan routing.
API-driven coordination: uses hub API for creating, updating, and stamping stories, with fail-safe fallbacks and deferred execution paths.
Coherence with epic macro-requirements: ensures spec aligns with epic goals and dependencies.

Quick Start

Invoke /spec with a STORYID or title to initiate the upstream ceremony and follow the CLAUDE.md lifecycle.

Frequently Asked Questions about spec

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

FAQPage Schema

How do I automate upstream requirements ceremonies for story management?▼

Automating upstream requirements ceremonies involves creating story skeletons, resolving epic context, and coordinating spec-writing activities end-to-end. This orchestration covers setup, exploration, writing, validation, and downstream routing with fail-open fallbacks.

What is an upstream gate review for spec writing?▼

An upstream gate review for spec writing is a validation ceremony ensuring structured content requirements—contexts, goals, acceptance criteria, risks, and edge cases—are fulfilled and stamped, enabling auditable upstream work before downstream routing.

How do I write specs that align with epic macro-requirements and dependencies?▼

To write specs aligned with epic macro-requirements, load epic context during the ceremony. This ensures story specs maintain coherence with epic goals and dependencies by applying structured content and gate-reviewed stamps.

Can I use spec automation for standalone workflows without linked epics?▼

Yes, spec automation applies to both stories linked to epics and standalone workflows. It covers the full setup, exploration, writing, and validation cycle, using fail-open fallbacks for unavailable APIs to maintain ceremony progression.

What are the limitations of automating story spec writing when APIs are unavailable?▼

When APIs are unavailable, direct story creation and stamping cannot occur. However, the automation applies fail-open fallbacks and deferred execution paths to continue coordinating the spec-writing ceremony without blocking workflow.

Does spec writing automation work with hub APIs for updating and stamping stories?▼

Yes, spec writing automation uses hub APIs for creating, updating, and stamping stories. It coordinates API-driven actions throughout the upstream ceremony, ensuring auditable gate-reviewed stamps are applied to story contexts.