Classify post-ship product deltas and route them to downstream APED skills.
npx skills add https://github.com/yabafre/aped-claude --skill aped-iterate
Please help me install this Agent Skill. Skill: aped-iterate Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-iterate Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-iterate
This Skill prevents mismatched follow-up work after a release by routing a post-ship delta to the correct downstream APED skill instead of trying to implement the change inside the router.
Use Case: You shipped feature X, but users now need feature Y or discover a gap—use this Skill to classify the required follow-up and route to the appropriate planning, quick-spec, or architectural decision step.
Use aped-iterate after you ship, by telling Claude Code something like: we shipped feature X, now we need Y to close the gap.
High-intent search queries and answers about installing and using this skill.
A post-ship router classifies the product delta by impact layer, blast radius, and reversibility, then hands off to the correct downstream workflow step. It prevents mismatched follow-up work after a release without implementing changes itself.
Running a short delta interview classifies the required follow-up by asking about layer of impact, blast radius, and reversibility. This routes the change to appropriate planning, quick-spec, or architectural decision steps instead of guessing.
No, post-ship routing halts if a sprint worktree is active. It enforces an activation guard and routes only after something has actually shipped, such as a release, merge, or deployment.
No, post-ship routing produces a recommendation and user-invocation handoff without mutating artifacts. It runs discovery against recent merges and state, optionally checking an out-of-scope knowledge base.
You should not use post-ship routing when a story is currently in-flight or before anything has shipped. It applies only when a user requests iteration after a merge, release, or deployment and no sprint worktree is active.
jeffdevilleAutomate skill activation when users mention trigger phrases in conversation.
maxwell2732Generate Spec delta and Plans.md tasks from input requirements.
joyce820309Create isolated Git worktrees for feature development workflows.
CANTAGESTUDIOAssess refactoring risk across blast radius, reversibility, and test coverage for go/no-go decisions.
