mpazaryna
- 42 skills
- 0 followers
- 2 days ago last updated
- ▌
- ▌ Orchestra Eval · mpazarynaGrade 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 skill was executed.
- ▌ Orchestra Plan · mpazaryna bundlePlanning 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 Spec · mpazaryna bundleGenerate 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.
- ▌ Yoga Professor · mpazaryna bundleEvaluate 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.
- ▌ Orchestra Merge · mpazaryna bundleMerge 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 Usher · mpazarynaOrient 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.
- ▌ Kairos Knote · mpazaryna bundleCapture a quick timestamped thought as a knote. Use when logging a thought, observation, decision, or anything worth capturing mid-day.
- ▌ Orchestra Devlog · mpazaryna bundleWrite 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 will need to know.
- ▌ Orchestra Review · mpazaryna bundleReview 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 Ticket · mpazaryna bundleCapture 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.
- ▌ Dev Skills Auditor · mpazaryna bundleAudit 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.
- ▌ Kairos Review · mpazaryna bundleRun a review at weekly, monthly, quarterly, or yearly zoom — synthesize notes, surface patterns, generate retrospective. Use when running periodic reviews.
- ▌ Orchestra Gherkin · mpazaryna bundleGenerate 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 Program · mpazaryna bundleExplain 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 Roadmap · mpazaryna bundleBootstrap 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.
- ▌ Yoga Orchestrator · mpazaryna bundleCoordinate yoga class planning by routing queries to specialist skills and synthesizing responses. Use when planning a yoga class, building sequences, or researching poses.
- ▌ Kairos Kickoff · mpazaryna bundleQuick morning orientation — surface ClickUp tasks, carry-overs, project gaps, and intensity patterns. Use when starting the workday.
- ▌ Orchestra Scaffold · mpazaryna bundleScaffold 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.
- ▌ Feynman Inquiry · mpazaryna bundleDeveloper 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 Shutdown · mpazaryna bundleEnd-of-day capture — ClickUp completion check, uncommitted work, intensity, tomorrow's frog. Use when closing out the workday.
- ▌ Writing No Slop · mpazaryna bundleClean, 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 Implement · mpazaryna bundleExecute 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 Milestone · mpazaryna bundleReview 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.
- ▌ Yoga Anatomy Expert · mpazaryna bundleProvide yoga anatomy expertise — biomechanics, contraindications, modifications, and anatomical rationale behind postures. Use when a teacher needs safety guidance or modification options for poses.
- ▌ Clickup Backfill · mpazarynaEnsure 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.
- ▌ Feynman Decision · mpazaryna bundleAnalyze technical options with structured comparison matrices, scoring, and ADR draft generation. Use when the user needs help choosing between technologies, architectures, or implementation approaches.
- ▌ Yoga Theme Developer · mpazaryna bundleCraft yoga teaching narratives, verbal cues, and thematic arcs that connect poses to meaningful intention. Use when developing the storytelling layer of a yoga class.
- ▌ Dev Distribution Audit · mpazaryna bundleAudit 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 installed skill is missing or duplicated.
- ▌ Yoga Asana Strategist · mpazaryna bundleDesign yoga sequences — class structures, pose progressions, and balanced practices. Use when building a yoga class sequence or evaluating pose flow.
- ▌ Kairos Weekly Plan · mpazaryna bundleDraft the start-of-week plan — project triage, load calculation, and priority setting. Use when beginning a new work week.
- ▌ Kairos Weekly Finalize · mpazaryna bundleFinalize 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.
- ▌ Swiftui Submission Prep · mpazaryna bundleReview 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.
- ▌ Dev Enforcer · mpazaryna bundleReview and validate implementation quality — catch workarounds, simulated data, incomplete implementations, and shortcuts. Use when checking if a feature is genuinely working end-to-end.
- ▌ Cf Hono · mpazaryna bundleHono framework patterns for Cloudflare Workers: routing, middleware, type-safe handlers, request validation, error handling. Use when building APIs with Hono on Cloudflare.
- ▌ Swift UI · mpazaryna bundleSwiftUI implementation patterns for building polished iOS/macOS apps. Use when building views, managing state, creating layouts, implementing animations, or structuring app architecture in SwiftUI.
- ▌ Dev Playwright · mpazaryna bundleGenerate 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.
- ▌ Orchestra Adr · mpazaryna bundleCapture 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 · mpazarynaConductor 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 nobody at the keyboard — the session must leave the repo in a state the next session (or a human) can pick up cold.
- ▌ Orchestra Prd · mpazaryna bundleDefine 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, or a spike finding.
- ▌ Orchestra Uml · mpazaryna bundleGenerate 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.
- ▌ Swift Lang · mpazaryna bundleMaster 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.