Speck.Pull Upstream — Testing skill for Claude Code
Pull a specific spec-kit release from upstream GitHub repository.
How to install Speck.Pull Upstream
Installs to ~/.claude/commands/nprbst-speck-speck.pull-upstream.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/nprbst/speck/HEAD/.claude/commands/speck.pull-upstream.md -o ~/.claude/commands/nprbst-speck-speck.pull-upstream.md Restart Claude Code, or start a new session, for it to be picked up.
What Speck.Pull Upstream does
Pull a specific spec-kit release from upstream GitHub repository.
Alternatives in Testing
- Gstack — 15,000+ Garry Tan's exact Claude Code setup: 6 opinionated tools that serve as CEO, Eng Manager, Release Manag 33.9k ★
- Notion Spec To Implementation — Convert Notion specs into linked implementation plans and tasks 14.6k ★
- Claude Code Spec Workflow — Automated Kiro-style Spec workflow for Claude Code 3.6k ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Speck.Transform Upstream
Transform upstream spec-kit release into Speck's Bun TypeScript implementation
Speck.Check Upstream
Check for available spec-kit releases from upstream GitHub repository
Verify Spec
Verify that a generated spec document preserves all upstream requirements and has no structural quality issues
Propagate
Use after editing an upstream doc (PRD/SRS/tech-design/feature-spec) to propagate changes downstream and keep
Sdlc Refresh
/sdlc-refresh — Back-Propagate a Built Spec into Its Upstream Artifacts
Spectastic.Explore
Build to learn — scaffold a quarantined exploration you build loosely (SDD ceremony off, thin principles floor
Related Agents
Cube Project Reviewer
Use this agent to review a pull request against CubeSandbox project-specific conventions and release gates tha
Git Pull
Safely pull updates (fork/upstream aware), stash-first, resolve conflicts via memory-bank context, no auto-sta
Vuln Discloser
Re-verifies confirmed findings against the latest upstream release and drafts maintainer-ready security adviso