Menu
SkillsMP has collected 28 skills from liza-mas/liza. Open a skill to review its source and details.
Showing 28 of 28 collected skills.
Operate a running §BRAND_NAME_TITLE§ multi-agent run from outside the agent pool: keep the orchestrator healthy, review checkpoints, recover stalls, wire agent environments, plan the next run, and escalate to the human only at genuine forks. Use when…
Pre-commit Clean Code refactoring
Produce legacy PRD-format SMARC specifications. Use only when the user or assigned task explicitly names detailed-spec-writing; never infer activation from requests to write an objective, goal, requirements, specification, plan, or PRD.
Analyze §BRAND_NAME_TITLE§ agents logs
Capture project-specific operational lessons from mistakes, discoveries, and hard-won insights
Two-sided code review protocol — reviewers raise findings, authors answer them. Use when reviewing code (PRs, pending changes) or when responding to review feedback, review comments, or a rejected verdict.
Surface alternatives — different ways to address the same need.
Coordinate Pairing-mode doer/reviewer sessions through a Markdown blackboard. Use when the user invokes /adversarial-pairing with role and blackboard-path arguments or asks multiple pairing agents to coordinate plan review, implementation, staged code review,…
Analyze §BRAND_NAME_TITLE§ `§BRAND_PROJECT_DIRNAME§/agent-prompts/` and `§BRAND_PROJECT_DIRNAME§/agent-outputs/` from a context-engineering perspective: prompt payload shape, context budget use, cacheability, duplicated or missing context, instruction…
Generate and curate Claude-oriented bash-policy project rules. Use to run bash-policy export/report, review .bash-policy-candidates.yaml from Claude settings, update .bash-policy.yaml, normalize command-shape identities, or validate bash-policy configuration.
Assess whether an input document is ready for a specific §BRAND_NAME_TITLE§ MAS entry point. Use when a user asks whether a goal, functional spec, detailed spec, technical spec, PRD, story bundle, architecture plan, or other source document is solid enough to…
Define component boundaries, interfaces, and structural decisions for a change
Summarize artifacts produced by §BRAND_BINARY_NAME§ agents for human checkpoint review
Quantitative and qualitative code quality assessment with prioritized refactoring recommendations
Transform vision documents into structured epics that bound story-writing
Context-efficient delegation to subagents (read-only default, READ-WRITE opt-in)
Software Architecture Review Protocol
Systemic Coherence and Risk Analysis
Transform requirements into user stories for coding tasks
Backfill missing ADR from git history and documentation
Black-Box Red Testing — red tests that expose real bugs
Backfill function-level contracts (docstrings, type annotations) where missing. Report unresolvable gaps with misuse scenarios. Incremental by default (state-driven).
Backfill missing specifications, reconcile spec/code drift, maintain changelog.
Find bugs by writing tests that should pass but don't. Invoke manually on user-chosen scope (commits, files, or coverage threshold). Outputs red tests with structured rationale. Use when user asks to "stress-test", "find bugs in", "attack", or "break" code.
explain complex ideas as Richard Feynman
Specification Review Protocol
Debugging Protocol
Test Protocol