ReddRadar
Topic: typescript
2,004 skills in this topic.
-
maestro:prompt-leverage
Strengthen a raw user prompt into an execution-ready instruction set for Claude Code, Amp, Codex, or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
ReinaMacCredy/maestro 26
-
maestro:status
Interpret feature progress, detect problems, and recommend next actions based on maestro status output.
ReinaMacCredy/maestro 26
-
maestro:agents-md
Use when bootstrapping, updating, or reviewing AGENTS.md — teaches what makes effective agent memory, how to structure sections, signal vs noise filtering, and when to prune stale entries
ReinaMacCredy/maestro 26
-
maestro:brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
ReinaMacCredy/maestro 26
-
maestro:debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
ReinaMacCredy/maestro 26
-
maestro:design
Deep discovery and specification for ambitious features. Full BMAD-inspired interview with classification, vision, journeys, domain analysis, and FR synthesis. Same output contract (spec.md + plan.md) as a standard feature but far richer. Use for multi-component systems, regulated domains, or unclear requirements.
ReinaMacCredy/maestro 26
-
maestro:dispatching
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
ReinaMacCredy/maestro 26
-
maestro:docker
Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
ReinaMacCredy/maestro 26
-
maestro:implement
Execute feature tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams, Sub Agent Parallels. Use when ready to implement a planned feature.
ReinaMacCredy/maestro 26
-
maestro:new-feature
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
ReinaMacCredy/maestro 26
-
maestro:next-move
Strategic analysis of a project to identify the single highest-leverage, most innovative addition. Use when the user asks what to build next, what the most impactful improvement would be, what's missing, or any question about strategic direction and priorities. Also use when stuck choosing between competing features.
ReinaMacCredy/maestro 26
-
maestro:note
Capture decisions, constraints, and context to persistent memory. Global memory is injected into every session and implementation run. Per-feature memory tracks working context.
ReinaMacCredy/maestro 26
-
maestro:parallel-exploration
Use when you need parallel, read-only exploration with task() (Scout fan-out)
ReinaMacCredy/maestro 26
-
maestro:plan-review-loop
Deep-review any plan (maestro, Codex, Claude Code plan mode, or plain markdown) using iterative subagent review loops with BMAD-inspired adversarial edge-case discovery. Spawns reviewer subagents that find issues using pre-mortem, inversion, and red-team techniques, auto-fixes them with structured fix strategies, and re-reviews until the plan passes with zero actionable issues. Use when the user says 'review the plan', 'deep review', 'check the plan thoroughly', 'review loop', 'validate before approving', or wants rigorous plan validation before execution. Also use proactively before plan-approve when the plan is complex or high-risk.
ReinaMacCredy/maestro 26
-
maestro:prompt-leverage
Strengthen a raw user prompt into an execution-ready instruction set for Claude Code, Amp, Codex, or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
ReinaMacCredy/maestro 26
-
maestro:revert
Git-aware revert of feature, phase, or individual task. Safely undoes implementation with task state rollback.
ReinaMacCredy/maestro 26
-
maestro:review
Code review for a feature against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
ReinaMacCredy/maestro 26
-
maestro:simplify
Review changed code for reuse, quality, and efficiency, then fix issues found. Use after implementing a task or feature -- catches duplication, hacky patterns, and wasted work before review.
ReinaMacCredy/maestro 26
-
maestro:tdd
Use when implementing any feature or bugfix, before writing implementation code
ReinaMacCredy/maestro 26
-
maestro:verification
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
ReinaMacCredy/maestro 26
-
maestro:visual
Create interactive HTML visualizations of maestro state and debug data
ReinaMacCredy/maestro 26
-
cli-for-agents
Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.
ReinaMacCredy/maestro 26
-
maestro-dev
Development workflow for maestroCLI itself. Encodes the hexagonal architecture pattern (port -> adapter -> use-case -> command -> MCP tool -> test) and project-specific conventions. Use when implementing new maestro features, adding CLI commands, extending the MCP server, creating new adapters, modifying ports, writing use-cases, or debugging maestro's own code. Also use when you need to understand how maestro's layers connect or where to put new code.
ReinaMacCredy/maestro 26
-
maestro-pipeline-test
Run a full end-to-end smoke test of all maestro CLI commands in a single session. Use this skill when testing the maestro pipeline, verifying tool installation, validating a maestro setup, or checking that all tool groups work (feature, plan, task, memory, meta, graph, handoff, search). Trigger on "test maestro", "smoke test", "pipeline test", "verify all tools", "run pipeline test", or whenever the user wants to confirm maestro is functioning correctly -- even if they just say "does it work?" in a maestro context.
ReinaMacCredy/maestro 26