pipekit

Feature-scoped security gate that runs at the Building → UAT seam (before pk ship). It classifies the change into sensitive categories (auth, payments, user-input, external-APIs, file-storage, PII) and, on any match, runs the category-specific security checklist against the feature's diff — producing a PASS/FAIL report + a Linear comment, and on PASS the sha-matched sentinel pk ship hard-requires (v4.17.0) on any project with a categories file. It does not transition state. Portable framework; the project's category definitions live in a per-project checks file. Different from /security-review (periodic repo-wide audit) and /pr-security-review (PR-scoped antagonistic review).

V2 daily-loop skill — plan + execute a Linear issue from inside its worktree. Use after pk branch opens a worktree. Use when an Approved Linear issue is ready for implementation. Native-on-Workflow is the sole executor (v4.0.0 removed the pluggable vbw backend).

Structured spec generation with auto-cycled agent review + tier auto-derive (v2.7.0-rc1+). Use when a Linear issue moves to spec stage. Use when writing/refining a feature spec before /work. Use when /spec-validator flags gaps.

Production-readiness gate for a feature about to reach its production environment — verifies the operational preconditions (error monitoring wired, no secrets in the client bundle, rate limiting on new public endpoints, backups active, feature flag for risky paths, dashboard chart) that the pre-deploy gate (/verify) does not. Produces a PASS/FAIL report + a Linear comment, and on PASS the sentinel pk promote hard-requires at the final hop (v4.17.0) on any project with a checks file; it does not transition state. Portable framework; concrete checks live in a per-project checks file. Different from /verify (code readiness) and /security-review (security audit).

verify — tier-aware evidence-gated pre-deploy gate. tier:standard|heavy write Logs/Verify/<date>/<id>/{evidence.txt,reality-check.md,verify-complete.md}; tier:quick writes only verify-complete.md on PASS. pk ship gates on a verify-complete.md whose sha matches HEAD. Use when a Linear issue is ready for verify (Stage 3). Use when /work finished and you need a Pass/Partial/Fail verdict per AC before pk ship.

Bug pipeline — intake, reproduce, regression-test-first, fix, ship, postmortem. Wraps /work and pk ship with discipline gates. Invoke when a bug is reported or spotted. Linear is the source of truth — resume by passing the issue ID.

Pluggable-engine PR review (pr-review-toolkit agents by default, built-in fallback) with two-axis severity×confidence triage and interactive remediation. Use when a PR needs review + structured fix triage. Use when pk ship --review surfaced findings. Use to address an existing review via --from-review. Different from /pr-security-review (security-only).

Security-focused antagonistic PR diff review. Use when a PR touches migrations, RLS, SECURITY DEFINER, auth, or Server Actions on privileged tables. Use before merge of any security-sensitive change. Different from /security-review (repo-wide) and /pr-fix (broad review).

Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.

Fast Linear placement janitor — finds orphaned / untriaged / unprioritized issues across all open states and batch-homes them. Use after pk done, before a phase, or whenever follow-ups have piled up. Propose-then-apply, importance-aware. Placement only (where does it belong?), not disposition (is it worth doing? — that's /brainstorm-review).

Build a staged roadmap from strategy docs and author it directly into Linear as the native initiative surface — Initiatives (i{N}. initiatives), Projects (P{N}. sub-phases), and Issues. Use as Stage 0 step 6 after /strategy-create, when bootstrapping the Linear hierarchy for a new project.

Write the session log to Logs/Sessions/<date>_<HHMM>.md before /exit. Captures narrative — what shipped, decisions, lessons, outstanding work. Run as the last command of every Claude session in a Pipekit project.

Rolling parallel agent queue across isolated worktrees. Use when batching multiple Approved Linear issues for parallel execution. Use when phase has independent issues with no shared blockers. Up to 4 workers, dependency-aware.

Run plan-reviewer agent against a PLAN.md before execution. Use after /work plan phase and before approving execution. Use when you need an independent gate catching scope drift, atomicity failures, test gaps. Requires a fresh chat.

Orchestrate full Stage 0 project bootstrap — concept through first phase. Use when initializing a new Pipekit project. Use when adopting Pipekit into a brownfield repo. Auto-detects greenfield/brownfield/inherited mode.

Bootstrap strategy docs from a project definition. Use after /define produces a project definition. Use as Stage 0 step 3 before /roadmap-create. Configurable doc set; counterpart to /strategy-sync which updates existing docs.

Update Strategy docs to reflect what actually shipped. Use after a feature lands in prod and Strategy docs drifted. Use at phase close to reconcile docs with reality. Use a fresh chat — recall contaminates the diff.

Batch-triage untriaged Linear issues — Now/Later/Kill verdict per item. Use when the brainstorm backlog has stacked up. Use before /phase-plan to clean the candidate pool. EXPAND/HOLD/REDUCE framework with scope reduction on Now items.

Analyze a feature idea, assess feasibility, file Linear issue. Use when the user shares a raw idea mid-session. Use when scoping a feature before /light-spec. Produces a triaged Linear ticket, not a full spec.

Confirm and advance the current execution initiative on the Linear-native surface — derive the active i{N}. initiative / P{N}. project, promote its issues to Needs Spec, and roll the initiative pointer forward by flipping Linear initiative/project state. Use when an initiative is closing and you need to open the next one.

Recommend the next pipeline step based on current project state. Use when unsure which Pipekit skill to run next. Use after finishing a step and wanting a deterministic "what now?" answer. Reads filesystem + Linear, not memory.

Empirical pre-flight checks on a Linear issue's spec. Use right before /work consumes a spec. Use when a spec has been sitting in Approved for >1 week and reality may have drifted. Verifies file paths, line refs, deps. Read-only.

Reconcile strategy-doc / requirement drift against the Linear board's i{N}./I{N}.P{N}. initiative hierarchy. Use when issues are mis-placed across projects, or initiatives/projects drift from the naming convention (projects are named I{N}.P{N}.; bare P{N}. is legacy-valid). Linear is the source of truth; there is no PHASES.md/linear-map.json to sync.

Apply Spec Review Agent feedback to a Light Spec — surgical edits only. Use when the Spec Review Agent posted unresolved blockers. Use when iterating a spec without rewriting from scratch. Detects stalemate loops.

Linear issue workflow helper. Use when triaging a Linear ticket. Use when transitioning state outside /work or /verify. Use when you need a structured comment template.

Fetch, prioritize, and execute Linear tasks systematically. Use when you want a single skill to walk through ready Linear issues end-to-end. Use as a lighter alternative to /linear-todo-runner when running serially.

Periodic repo security audit (not PR-scoped — see /pr-security-review for that). Use when auditing the whole repo for auth, secrets, RLS, OWASP baselines. Use when scoping a security pass before a release.

Periodic financial-accuracy review for finance/calculation-heavy projects — cross-layer parity audit (DB view ↔ server calc ↔ UI), severity-ranked report, recurring-WIT lifecycle. Portable framework; concrete checks live in a per-project checks file. Different from /security-review (security) and /pr-security-review (PR-scoped).

Idea→Draft-PR autopilot for simple WITs — chains /brainstorm → /light-spec (auto-cycle to Approved) → pk branch → /work (auto verify+ship), advancing on success and stopping only when something needs you. Quick/Standard tier only. Invoke with /pk-express "<idea>" or resume with /pk-express <ISSUE-ID>.

Pull latest Pipekit skills, SOPs, templates from GitHub into current project. Use when adopting a new Pipekit release. Use when a synced skill has drifted from upstream. Never touches project-specific files.

Distill a raw project idea into a structured concept brief. Use when starting a greenfield Pipekit project. Use as the first Stage 0 step before /define. Skip for brownfield/inherited projects.

Turn a validated concept brief into a full project definition. Use after /concept produces a viable brief. Use before /strategy-create as Stage 0 step 2. Outputs stages, roles, workflows, success criteria.

Draft a CHANGELOG entry from git commits between tags. Use when cutting a release and need a starting CHANGELOG block. Use after a version bump to regroup commits into canonical sections. Read-only on git and CHANGELOG.md — outputs to stdout.

Sync skill index docs after skills change. Use when a skill is added, renamed, or removed under .claude/skills/. Use when Skills_SOP.md skill list has drifted from the directory. Keeps the catalog current.

Audit a technical spec for completeness and consistency. Use after /light-spec drafts a spec and before promoting to Approved. Use when a spec feels under-specified. Flags gaps for /light-spec-revise to close.

Start any unit of work — creates worktree + branch + optional Linear link

End a work session by capturing reflections, committing work, and creating a session log

Promote current feature branch to dev by creating a PR. Reads method.config.md for Linear state IDs, pre-deploy gate, and stack-specific values. Verifies pre-deploy gate, optionally pushes migrations, extracts Linear issue references, transitions issues to In Progress.

Experimental VBW-free variant of /launch. Spawns planning, dev, and QA agents directly via the native Agent tool. Use to A/B test whether VBW is still pulling its weight.

Open + close gate for a specced Linear issue. Validates readiness, transitions Linear status, hands off to VBW for plan/execute/verify, and transitions to UAT on close.