pull

Execute downstream stories from ready_to_pull to done with enforced gates.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ramontramontini/CTEDemo --skill pull-ramontramontini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull
Source: https://github.com/ramontramontini/CTEDemo/tree/main/.claude/skills/pull
Command: npx skills add https://github.com/ramontramontini/CTEDemo --skill pull-ramontramontini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pulling a story through downstream gates is complex and error-prone; this skill automates end-to-end execution with governance to ensure upstream and downstream steps are completed, validated, and shipped.

Core Features & Use Cases

  • End-to-end story execution from ready_to_pull through done with enforced gates.
  • Support for skeleton/specifying, resumed in_progress stories, and upstream epic fallbacks.
  • Context-rich spec display, TDD cycle, gate stamps, ship-review, and post-shipping verification.

Quick Start

Run /pull STORYID or /pull Story Title to execute a story from ready_to_pull through done.

Frequently Asked Questions about pull

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

FAQPage Schema
How do I automate story workflow execution from ready_to_pull to done?

To automate story workflow execution end-to-end, you can run a pull command with a Story ID or Title. This triggers downstream execution, enforcing upstream gates, TDD cycles, and final quality gates before shipping.

How does TDD cycle enforcement work during story pull and ship-review?

TDD cycle enforcement during story pull validates that test-driven development steps are completed before transitions. It applies gate stamps and executes ship-review checks to ensure all downstream quality criteria are met prior to shipping.

Can I resume an in_progress story workflow with automatic epic fallbacks?

Yes, you can resume in_progress stories using the pull command. It supports automatic epic fallbacks and applies gating checks to route the story status correctly from its current state through to done.

What is the best way to enforce upstream gates for downstream story transitions?

The best way to enforce upstream gates for downstream story transitions is through an automated governance pull. It validates upstream dependencies, applies status routing, and secures gate stamps before allowing the story to ship.

Does the story pull skill support skeleton or specifying statuses?

Yes, the story pull skill supports stories in skeleton or specifying statuses. It identifies the current status, applies automatic epic fallbacks, and routes the story through the required gates to execute it end-to-end.

Why does my story workflow fail final quality gates before shipping?

Story workflows fail final quality gates when upstream dependencies are incomplete or TDD cycles lack validation. The pull skill enforces these gate stamps and ship-review checks to prevent premature shipping of unverified stories.