bdouble/pm-vibecode-ops
16 skills
$npx skills add bdouble/pm-vibecode-opsSkillInstalls
closure-log-aggregationUse 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…codex-finding-resolutionUse when Codex review returns findings, when processing codex_review_and_fix or codex_review results, when collecting a codex-delegate job with…divergent-explorationExplores 3-5 distinct approaches before committing to one. Use when: - Design decisions: "design", "architect", "plan", "how should we", "what's the best way"…epic-closure-validationValidates epic completion before closure. Use when: - Closing epics: "close epic", "finish epic", "complete epic", "epic done", "mark epic complete" - Checking…model-aware-behaviorEnforces verification over recall and prevents scope creep. Use when: - Acting on a claim from docs, project memory (AGENTS.md/CLAUDE.md), or a ticket without…mvd-documentationEnforces minimal, decision-focused documentation (WHY not WHAT).no-silent-deferralsUse 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…production-code-standardsEnforces production-grade code quality. Use when: - Writing code: "implement", "write code", "add feature", "fix bug", "create service", "build" - Detecting…security-patternsEnforces OWASP Top 10 security patterns during code writing. Use when: - Authentication: "authentication", "login", "password", "JWT", "OAuth", "session",…service-reusePrevents code duplication by requiring inventory check before creation.swarm-observabilityUse 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…swarm-phase-reportingUse when any workflow phase completes for a ticket — adaptation, implementation, testing, documentation, code review, codex review, or security review.systematic-debuggingUse when a test fails, a build errors, a runtime exception appears, or behavior is unexpected.testing-philosophyEnforces test accuracy over coverage quantity. Use when: - Writing tests: "write tests", "add tests", "test this", "improve coverage", "testing phase" - Fixing…using-pm-workflowGuides users through PM workflow phases and command sequence. Use when: - Asking for guidance: "what command", "which phase", "where do I start", "what's…verify-implementationRequires evidence before any completion claim. Use when: - Checking status: "is it done", "is this done", "are we finished", "ready for review", "create PR",…