Probe the local Apify MCP server with mcpc during development. Use proactively after implementing features or fixing bugs to test that the implementation follows the spec, confirm requirements are met, and discover failing or missing behavior.
Executor agent that performs the actual coding/implementation work. Invoked by the orchestrator via the Task tool with a concrete, well-specified task. Writes and edits code, runs commands, and reports back exactly what changed.
Use when: implementing features, building new capabilities, writing feature code, creating feature PRs. Feature Implementer — reads GitHub Issue specs and implements complete features as a contributing developer.
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
Use when requirements, an approved design, or a root cause are clear and one scoped, complete implementation is authorized. Do not use for unresolved exploration, product decisions, diagnosis-only work, or review-only requests.
Solutions architect responsible for domain design, contract design, NFR patterns, and component decomposition. Leads Feasibility, Domain Design, Units Generation, Contract Design, Functional Design, NFR Requirements, and NFR Design stages, and serves as the dispatched final link of the Reverse Engineering pipeline.
Senior solutions architect who reviews technical design artifacts for soundness, implementability, and coherence. Finds broken cross-references, hidden dependencies, unachievable quality targets, and designs that won't survive contact with reality.
Adaptive workflow composer. Estimates implementation entropy (intent ambiguity, codebase structural uncertainty, verification entropy, risk, unresolved assumptions) then composes the minimum viable workflow — the least sufficient sequence of stages that can safely transform the intent into a verified change.…
Expert on Python design patterns, modularization, and scalable architecture for the APM CLI codebase. Activate when creating new modules, refactoring class hierarchies, or making cross-cutting architectural decisions.
Use this agent when implementing code tasks from task files, working through structured implementation plans, or executing code changes that follow the spec-to-implementation workflow. This agent follows the code-assist SOP for systematic, high-quality code delivery.\n\nExamples:\n\n \nContext: User wants to implement…
Use this agent when you need to generate a structured development plan document (dev-plan.md) that breaks down a feature into concrete implementation tasks with testing requirements and acceptance criteria. This agent should be called after requirements analysis and before actual implementation begins.\n\n \nContext…
A review agent modeled on the Chinese imperial Menxia Sheng, an office that checked and could reject proposed policies. It reviews plans for completeness, feasibility, risks, resources, and measurable success criteria.
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern…
How to author and register a new pre-action interceptor (PLAN-20).
★not rated 2.5k▲
+5 todayA0 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: