mpazaryna-agentic-factory

Plugin mpazaryna-agentic-factory from marketplace cascade-ai-ml-agents-misc-2 in joshuarweaver/cascade-ai-ml-agents-misc-2. Commands read from the repo's manifest — 1 month ago.

Skills (50)

• dev-enforcer

  Review and validate implementation quality — catch workarounds, simulated data, incomplete implementations, and shortcuts. Use when checking if a feature is genuinely working end-to-end.

• dev-playwright

  Generate Playwright E2E tests by exploring websites and automating browser interactions. Use when the user wants to generate Playwright tests by exploring a website, or needs browser automation.

• dev-skills-auditor

  Audit plugin skills and agents for compliance with Claude Code best practices — checks frontmatter, descriptions, tool restrictions, structure, and naming. Use when improving plugin quality or before publishing.

• web-perf

  Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, de

• dev-distribution-audit

  Audit what a skill repository actually ships versus what its authors think it ships — silent shadowing, depth-limit invisibility, name-collision dedup, leaked project skills, and manifest drift. Use when publishing or restructuring a skill library, after moving skill directories, or when an installe

• agents-sdk

  Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, chat applications, voice agents, or browser automation. Covers Agent class, state management, callable RPC, Workflows, durable ex

• cf-hono

  Hono framework patterns for Cloudflare Workers: routing, middleware, type-safe handlers, request validation, error handling. Use when building APIs with Hono on Cloudflare.

• cloudflare-email-service

  Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing). Use when building email sending (Workers binding or REST API), email routing, Agents SDK email handling, or integrating email into any app — Workers, Node.js, Python, Go, etc. Also use for email deli

• cloudflare

  Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biase

• durable-objects

  Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with

• sandbox-sdk

  Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from

• swift-lang

  Master advanced Swift language features: macros, concurrency, generics, networking, testing. Use when working with Swift macros, async/await patterns, protocol design, or optimizing for performance. See swift-ui for SwiftUI-specific patterns.

• swift-ui

  SwiftUI implementation patterns for building polished iOS/macOS apps. Use when building views, managing state, creating layouts, implementing animations, or structuring app architecture in SwiftUI.

• swiftui-submission-prep

  Review SwiftUI apps for App Store submission readiness — guidelines compliance, code quality, metadata, and testing coverage. Use when preparing to submit iOS/macOS apps, checking App Store metadata, verifying accessibility, or addressing previous rejections.

• workers-best-practices

  Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards

• wrangler

  Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudfl

• clickup-backfill

  Ensure every .orchestra/work/ item has a corresponding ClickUp ticket. Creates missing tickets and writes the ID back into the PRD frontmatter. Use when backfilling a repo's work items into ClickUp.

• digest

  Extract key points from a URL (web or YouTube) and organize the output. Usage: /digest <url>

• feynman-decision

  Analyze technical options with structured comparison matrices, scoring, and ADR draft generation. Use when the user needs help choosing between technologies, architectures, or implementation approaches.

• feynman-inquiry

  Developer inquiry skill for technical investigation, validation, and decision-making. Use when exploring unfamiliar technology, validating approaches with spikes, comparing options, or making architecture decisions. Covers the full thinking process from "I don't know" to confident decision.

• kairos-kickoff

  Quick morning orientation — surface ClickUp tasks, carry-overs, project gaps, and intensity patterns. Use when starting the workday.

• kairos-knote

  Capture a quick timestamped thought as a knote. Use when logging a thought, observation, decision, or anything worth capturing mid-day.

• kairos-review

  Run a review at weekly, monthly, quarterly, or yearly zoom — synthesize notes, surface patterns, generate retrospective. Use when running periodic reviews.

• kairos-shutdown

  End-of-day capture — ClickUp completion check, uncommitted work, intensity, tomorrow's frog. Use when closing out the workday.

• kairos-weekly-finalize

  Finalize the weekly plan after reviewing and acting on decisions in ClickUp. Use when the draft weekly plan has been reviewed and is ready to lock.

• kairos-weekly-plan

  Draft the start-of-week plan — project triage, load calculation, and priority setting. Use when beginning a new work week.

• writing-no-slop

  Clean, human-sounding prose style guide that bans common LLM clichés, filler phrases, dramatic language, and vague vocabulary. Use when writing articles, documentation, blog posts, or any prose that should sound human and direct.

• orchestra-adr

  Capture an architectural decision record — document a decision that was made during work, why it was made, and its consequences. Use when a significant technical or process decision needs to be recorded for future agents and developers.

• orchestra-afk

  Conductor discipline for unattended (AFK) sessions — advance the work item from repo state, pause at human decisions by committing a gate file, resume from answered gates. The repo is the workspace; gates are files; approval is a commit. Use when running as a scheduled or headless session with nobod

• orchestra-devlog

  Write the engineer's journal — session logs, narrative progress notes, and git journals that capture the story behind the commits. The programme notes for whoever works here next. Use when capturing what happened during a work session, why decisions were made, or what a future agent or developer wil

• orchestra-eval

  Grade the outputs of an orchestra skill run against its eval assertions — reads produced files, checks each assertion, and writes a grading report. Use when an orchestra skill has just been run and its outputs need verifying — run `orchestra-eval <skill-name> [work-item-id]` in the project where the

• orchestra-gherkin

  Generate Gherkin scenarios from an orchestra PRD or spec — produces Feature/Scenario blocks in fenced gherkin markdown. Use when translating acceptance criteria or implementation steps into executable BDD scenarios.

• orchestra-implement

  Execute an approved spec — create a branch, work through each step, commit progress, and mark complete. Use when a spec is approved and ready for implementation.

• orchestra-merge

  Merge a reviewed implementation branch into main — resolve conflicts, close the work item, and clean up the branch. Use when an implementation has passed review and is ready to ship.

• orchestra-milestone

  Review milestones and project progress — diff materials table against repo state, surface gaps, check for orphaned work items, and propose next actions. Use when the user asks about milestones, project status, what to work on next, what's left to do, or wants to check progress on the roadmap.

• orchestra-plan

  Planning conductor — runs the full PRD → Spec → Gherkin loop in a single interactive session with human approval gates. Use when starting new work from a ticket or brief, or resuming an in-progress planning session.

• orchestra-prd

  Define the what and why for a piece of work — objective, success criteria, materials table, and context. The foundational Score document before any spec is written. Use when a piece of work needs to be scoped before execution — whether surfaced by a milestone review, a ticket, a stakeholder request,

• orchestra-program

  Explain what Orchestra is — a software development lifecycle encoded for agents, its SDLC roots, the pipeline, roles, file structure, status vocabulary, and skill index. Use when someone asks what Orchestra is, how it works, where its components come from, or where to start.

• orchestra-review

  Review a completed implementation branch against its spec and acceptance criteria — catch gaps, shortcuts, and quality issues before merge. Use when an implementation branch is complete and ready for review.

• orchestra-roadmap

  Bootstrap or manage the .orchestra/roadmap.md — interactive project setup when no roadmap exists, or status/update/add commands when one does. Use when setting up a new project's vision and milestones, checking project status, or updating the roadmap.

• orchestra-scaffold

  Scaffold the .orchestra/ agent knowledge base in a project — creates folder structure, templates, README, and ADR-000. Use when setting up a new project or adding .orchestra/ to an existing one.

• orchestra-spec

  Generate an execution spec from an approved PRD — define approach, steps, deliverables, acceptance criteria, and risks. Use when a PRD is approved and the work needs a concrete execution plan.

• orchestra-ticket

  Capture a work ticket as the starting point for the orchestra loop — read a brief, scaffold the work item folder, and set up for PRD and spec. Use when starting new work from a ticket, task, or brief.

• orchestra-uml

  Generate UML diagrams as Mermaid code and save them to .orchestra/uml/. Supports sequence, class, deployment, component, and state diagram types. Use when documenting system architecture, agent workflows, deployment topology, or state machines.

• orchestra-usher

  Orient at session start — read project state, surface what needs attention, and route to the right skill. Use when starting a work session, when unsure what to work on next, or any time a current read of project state is needed.

• yoga-anatomy-expert

  Provide yoga anatomy expertise — biomechanics, contraindications, modifications, and anatomical rationale behind postures. Use when a teacher needs safety guidance or modification options for poses.

• yoga-asana-strategist

  Design yoga sequences — class structures, pose progressions, and balanced practices. Use when building a yoga class sequence or evaluating pose flow.

• yoga-orchestrator

  Coordinate yoga class planning by routing queries to specialist skills and synthesizing responses. Use when planning a yoga class, building sequences, or researching poses.

• yoga-professor

  Evaluate yoga teaching readiness through scenarios, knowledge probes, and guided learning exercises. Use when a teacher wants to test their understanding or prepare for a class.

• yoga-theme-developer

  Craft yoga teaching narratives, verbal cues, and thematic arcs that connect poses to meaningful intention. Use when developing the storytelling layer of a yoga class.

Similar plugins