Routes full feature development through the SPipe and SStack orchestrator flow.
npx skills add https://github.com/ormastes/Spipe --skill sp-dev
Please help me install this Agent Skill. Skill: sp_dev Source: https://github.com/ormastes/Spipe/tree/main/.codex/skills/sp_dev Command: npx skills add https://github.com/ormastes/Spipe --skill sp-dev
It eliminates the ambiguity and inconsistent workflows that slow down full feature development by providing a single, explicit alias that routes work through the complete SPipe development pipeline.
Use it when you want a feature request to reliably traverse intake, research, design, SPipe specs, implementation, verification, and ship handoff.
Run /sp_dev with a clear description of what you want to build or fix, and let the full feature-development pipeline handle orchestration from start to ship.
High-intent search queries and answers about installing and using this skill.
Full feature development orchestration routes a requested change through the complete SPipe pipeline, covering intake, research, design, specs, implementation, verification, and ship handoff. You initiate this by providing a clear description of the feature request.
Yes, a single unified workflow handles bug fixes, refactors, and TODOs alongside feature work. It reliably traverses the full development lifecycle from intake to ship handoff, eliminating inconsistent ad-hoc processes.
The SPipe orchestrator flow handles namespace clarity by using the /sp_dev alias, keeping SPipe-scoped intent explicit in larger teams. It ensures consistent orchestration by following the standard SStack dispatch procedure.
The best way to ensure consistent behavior across dev orchestration aliases is to use the standard SStack dispatch procedure with no behavioral divergence. The /sp_dev, /dev, and /sstack aliases all follow identical orchestration logic.
No, you do not need to manually run separate stages for research, design, and verification. The pipeline automatically coordinates these steps sequentially as part of the end-to-end full feature development flow.
You should not use an end-to-end development pipeline for a TODO if the change only requires a partial or ad-hoc process. This pipeline is designed for TODOs requiring the complete intake, research, design, and ship handoff lifecycle.
eugenelimCoordinate Jira defect handling from intake to pull request and tracker update.
poisontr33sScan SESSION_HANDOFF_*.md files and route actions across Codex, Claude, and Gemini mailboxes.
ormastesRun the 8-phase SStack pipeline for development tasks.
valorisaEnforce a spec-first development pipeline with triage and phase gates.
