All authors

Claude Skills by kennedykjj
github.com/kennedykjj8 skills0 installs5 views
- DashboardOpens the factory's local dashboard (pool, live runs, logs, cost per card, review pages) in the browser. Started by "/sf:dashboard [--port N] [--no-open]".Votes: 0GitHub stars: 3
- DeployFactory pipeline 4, deploy — conflict resolution and fix rounds. The deploy itself is the script ~/.shipfloor/factory/deploy.sh, run by the dispatcher; this skill is called only when the script hands over merge conflicts with main, or a gate or CI that went red on top of main, and fixes them in the card's worktree. Started by the dispatcher or by "/sf:deploy <n>".Votes: 0GitHub stars: 3
- DevelopFactory pipeline 2, implementation (Tech Lead). Takes the next card from Ready for Dev (or the issue given), plans, has QA write failing acceptance tests, has each layer's engineer implement and hands the card to Validation. Started by the dispatcher or by "/sf:develop [n]".Votes: 0GitHub stars: 3
- RefineFactory pipeline 1 (Tech Lead). Takes the next card from Ready for Refinement (or the issue given), has the PO, UX/UI and Cybersec write their spec sections, writes architecture and test plan, and leaves the card in Spec Review. Started by the dispatcher or by "/sf:refine [n]".Votes: 0GitHub stars: 3
- ValidateFactory pipeline 3, validation (Tech Lead). Takes the next card from Validation (or the issue given), reruns the gates, reviews it (code, UX, security), has the owners fix blockers, opens or updates the PR, waits for CI and leaves the card in Staged. Started by the dispatcher or by "/sf:validate [n]".Votes: 0GitHub stars: 3
- DeployFactory pipeline 4, deploy — conflict resolution and fix rounds. The deploy itself is the script ~/.shipfloor/factory/deploy.sh, run by the dispatcher; this skill is called only when the script hands over merge conflicts with main, or a gate or CI that went red on top of main, and fixes them in the card's worktree. Started by the dispatcher or by "/sf:deploy <n>".Votes: 0GitHub stars: 3
- DevelopFactory pipeline 2, implementation (Tech Lead). Takes the next card from Ready for Dev (or the issue given), plans, has QA write failing acceptance tests, has each layer's engineer implement and hands the card to Validation. Started by the dispatcher or by "/sf:develop [n]".Votes: 0GitHub stars: 3
- ValidateFactory pipeline 3, validation (Tech Lead). Takes the next card from Validation (or the issue given), reruns the gates, reviews it (code, UX, security), has the owners fix blockers, opens or updates the PR, waits for CI and leaves the card in Staged. Started by the dispatcher or by "/sf:validate [n]".Votes: 0GitHub stars: 3