Automate upstream requirements ceremonies for stories with skeleton creation and spec writing.
npx skills add https://github.com/ramontramontini/CTEDemo --skill spec-ramontramontini
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
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.
Invoke /spec with a STORYID or title to initiate the upstream ceremony and follow the CLAUDE.md lifecycle.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
ramontramontiniOrchestrate epic story batches with gate enforcement and topological ordering.
ramontramontiniExecute downstream stories from ready_to_pull to done with enforced gates.
amitmishra-bylddExecute story implementation from context-filled spec files with status transitions.
guma154-cmdCreate and validate user stories from PRDs for Agile sprint planning.
