bdouble

bdouble/pm-vibecode-ops

Command

Adapt ticket requirements to codebase patterns, producing implementation guide.

bdouble/pm-vibecode-ops

Command

Close completed epic with a Convention Guard Audit (patterns ship guards or are tagged prose-only), impact-bar-disciplined follow-up tickets (capped at 3), guard-or-ratchet boundary fixes for cross-cutting concerns, Considered-but-not-pursued closure-log, downstream impact propagation, and CLAUDE.md updates with prose…

bdouble/pm-vibecode-ops

Command

Review code quality, patterns, and architectural consistency (security issues logged only).

bdouble/pm-vibecode-ops

Command

Cross-model code review using OpenAI Codex for bug detection, security analysis, and surgical fixes.

bdouble/pm-vibecode-ops

Command

Analyze codebase and create comprehensive technical discovery report as a Linear ticket in the project, documenting patterns, architecture, and service inventory for implementation phases.

bdouble/pm-vibecode-ops

Command

Create comprehensive documentation for implemented features, including API docs, user guides, and technical architecture documentation with real code examples.

bdouble/pm-vibecode-ops

Command

Recurring cross-epic entropy audit — mechanical census + judgment review with a machine-diffable scorecard (prose-only count, guard/ratchet inventory, dead machinery, test ballast) and a doc-truth sweep of project memory. The consolidator role no per-ticket phase performs.

bdouble/pm-vibecode-ops

Command

Transform PRD and business requirements into capability-focused Linear epics that provide engineering teams with clear functional requirements and business context without prescribing technical implementation.

bdouble/pm-vibecode-ops

Command

Launch the epic-swarm-workflow dynamic workflow — a resilient, right-sized multi-agent swarm over a Linear epic (per-ticket pipeline sized to effort; STANDARD tickets run adapt→implement→test→docs→review→codex→security→merge, NOCODE/SMALL collapse to build→review→merge; reviews fail-closed).

bdouble/pm-vibecode-ops

Command

Orchestrate sequential execution of epic sub-tickets using dependency-aware tier scheduling with worktree isolation and full per-ticket workflow pipelines.

bdouble/pm-vibecode-ops

Command

Orchestrate all ticket workflow phases (adaptation → implementation → testing → documentation → codereview → codex-review → security-review) automatically.

bdouble/pm-vibecode-ops

Command

Generate or update service inventory files for frontend and backend to track reusable components and prevent duplication.

bdouble/pm-vibecode-ops

Command

Execute code implementation based on adaptation guide, focusing on delivering functionality strictly within ticket scope following established patterns.

bdouble/pm-vibecode-ops

Command

Technical decomposition of Linear epics into actionable implementation tickets with proper dependencies and technical specifications, using epic tickets as primary input with optional PRD, discovery report, and additional context.

bdouble/pm-vibecode-ops

Command

Complete a security review of the pending changes on the current branch and update Linear ticket with findings.

bdouble/pm-vibecode-ops

Command

Render an observability dashboard for an epic or solo ticket — phase activity, deferral discipline, impact-bar rejections, codex findings, follow-up cap, profile distribution. Shells out to scripts/swarm-stats.sh.

bdouble/pm-vibecode-ops

Command

Generate comprehensive test suites with edge case coverage, security testing, and performance validation for implemented features.

bdouble/pm-vibecode-ops

Hook

Runs when a session starts, executing session-start.sh. From bdouble/pm-vibecode-ops.

bdouble/pm-vibecode-ops

Skill Claude CodeCodex

Use when running /close-epic, when about to file the epic closure comment, when an operator asks "what did we consider but not pursue in this epic", or when about to summarize an epic's surfaced-but-deferred work. Also use when about to grep sub-ticket comments for closure-log entries by hand, when about to skip a ###…

bdouble/pm-vibecode-ops

Skill Claude CodeCodex

Use when Codex review returns findings, when processing codexreviewandfix or codexreview results, when collecting a codex-delegate job with codexstatus/codexresult, when cross-model review report contains P0-P3 items, or when about to post a Codex review report to Linear. Also use when about to file a Codex finding as…

bdouble/pm-vibecode-ops

Skill Claude CodeCodex

Use when about to defer in-scope work or file a follow-up ticket for something observed during execution — saying "I'll defer this", "follow-up ticket", "out of scope", "future work", "handle separately", writing a Deferred Items entry, classifying AC-DEFERRED, or advancing a phase with known unfinished in-scope work.…

bdouble/pm-vibecode-ops

Skill Claude CodeCodex

Use when user asks "is the workflow actually working", "are we deferring too much", "what's our profile mix", "did the impact bar help", "how many follow-ups did this epic file", "what's the codex auto-fix rate", or any other meta-question about pm-vibecode-ops execution patterns. Also use when about to count Linear…

bdouble/pm-vibecode-ops

Skill Claude CodeCodex

Use when any workflow phase completes for a ticket — adaptation, implementation, testing, documentation, code review, codex review, or security review. Use when processing agent results, when about to advance to the next phase, when a ticket status is being updated, or when an agent has returned a structured report.…

bdouble/pm-vibecode-ops

Skill Claude CodeCodex

Use when a test fails, a build errors, a runtime exception appears, or behavior is unexpected. Also use when about to "just try" a fix without stating a hypothesis, when the second or third fix attempt has failed, when tempted to change multiple things at once, or when saying "it's broken", "not working", "failing"…