Rolaand-Jayz

Project-local design wrapper that specializes anti-slop app design for vibejam3’s premium editorial, book-like guide-production workflow.

Project-local wrapper that applies the shared end-to-end autonomy stack to vibejam3 using the repo’s phase-0 inspection, PRD pack, and phase-specific skill chain.

Project-local completion gate tuned to vibejam3's acceptance criteria and trust-critical surfaces. Decides whether a slice or phase is honestly complete.

Project-local end-to-end autonomy stack tuned to vibejam3's PRD-first, guide-production workflow. Selects the minimum skill stack for autonomous execution.

Project-local handoff pack tuned to vibejam3's PRD structure, milestone plan, and file layout. Produces resumable state for agent-to-agent transfers.

Project-local phase-0 skill for vibejam3 that inspects the actual workspace, detects the build/test/runtime stack, and reports readiness and missing pieces before implementation starts.

Project-local PRD-to-deploy accelerator tuned to the vibejam3 guide production system. Drives the fastest safe path from PRD to working code without skipping proof.

Project-local PRD gap closure tuned to the vibejam3 PRD pack structure. Finds blockers, confirms assumptions, and classifies unresolved questions specifically against the COPILOT-PRD-vibe1 documents.

Discover the personal shared skill pack available in this environment and choose the right reusable workflow for this repository. Use when you need routing guidance across specification, anti-stub, security, release-readiness, hardening, and optimization skills without duplicating the whole pack into the repo.

Run the full no-stubs cleanup workflow by invoking the stub-sweep, destub-plan, and destub-implement skills in order. Use when you want one slash command to audit the repository for stubs, create a remediation plan, and then implement real feature behavior without introducing new stubs.

Implement a de-stub remediation plan end-to-end. Use when you already have a stub findings document and a de-stub plan and need to replace stubbed features with real, ready-to-use behavior, tests, and validation without introducing new stubs.

Turn a stub audit document into a concrete remediation plan. Use when you have a stub findings report and need a systematic, no-stubs implementation plan that converts each stubbed feature into a complete, ready-to-use feature without writing placeholder behavior.

Systematically hunt stubs, placeholders, fake completion paths, TODO-backed features, NotImplemented-style stand-ins, and similar unfinished behavior across an entire repository. Use when you need a full stub audit of every tracked user-authored file and a documented findings report without fixing anything yet.