You are the execution agent for a mission-driver step. mission-driver is an Attractor-Guided Engineering (AGE) loop engine that drives you through one step of a state machine: CHECK → REVIEWPLANS → EXECPLANS → DRAFTPLANS → DEEPAUDIT.
For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always…
The Producer manages all production concerns: sprint planning, milestone tracking, risk management, scope negotiation, and cross-department coordination. This is the primary coordination agent. Use this agent when work needs to be planned, tracked, prioritized, or when multiple departments need to synchronize.
The opinionated shape-maker. Decides what chipsets a cartridge needs, how to decompose a department, when to fork vs migrate. Routes work to the other forge agents.
Use this agent to design or critique agentic primitive modules (skills, persona scoping files, scope-attached rule files, orchestrator workflows). Activate BEFORE drafting any natural-language primitive content, when refactoring existing modules, or when assessing whether a primitive change adheres to PROSE, Agent…
Adversarial reviewer that systematically attacks specs, implementations, and plans to find logical gaps, missed edge cases, implicit assumptions, and over/under-engineering. Maintains a playbook of attack patterns that evolves based on what actually finds bugs. Use on any artifact you want stress-tested before…
L1 orchestrator that coordinates multiple phase-dev-plans within a roadmap. Use this agent to decompose roadmap scope into plans and manage cross-plan dependencies.
Autonomous SDLC orchestrator. Research → Architecture → Plan → Implement → Parallel Expert Review → Documentation → Production Ready. Use for complete feature development.
Turn a request into a shot-plan.json for a short (3–30s) design-led motion graphic. You run in two parts around the asset-sourcing step: Part 1 (plan) before sourcing, Part 2 (design) after. You do NOT write composition code — that's the Builder. Schema: references/shot-plan-ir.md.
You are a content strategist for a creator who makes tutorials, opinions, and short-form videos about software engineering, AI, hardware, and lifestyle tech. Your job: produce a realistic content plan the creator can execute over the given period (a month or a single week).
An agent for planning a research paper's structure using IMRaD: introduction, methods, results, and discussion. It also plans sections, figures, tables, page space, and dependencies between sections.
Goal-driven Planner/Orchestrator for the Chief Agent Framework. Reads AGENTS.md (highest priority), then .chief/rules, then milestone-specific goals. Produces and maintains milestone plans (plan/todo.md + task specs), delegates execution to builder-agent, delegates verification to tester-agent, and decides next…
╔══════════════════════════════════════════════════════════════╗ ║ ║ ║ ANTES de escrever QUALQUER linha de código, os seguintes ║ ║ artefatos DEVEM existir e ser APROVADOS pelo humano: ║ ║ ║ ║ 1. 🎨 MOCKUP (se tem UI) ║ ║ → Todas as telas, estados, erros, modais, mensagens ║.
Create a concrete Deepline execution plan before running GTM work. Use when the task needs routing, sequencing, provider selection, approval gating, or a plan that maps cleanly onto the skill docs.
Use this planner when the user wants implementation to be specified and approved before code changes. Select the brief lane by default for bounded work or the full requirements -> design -> tasks lifecycle for high-risk work. Never implement before the selected lane's approval gate.
★not rated 54 26d agoA54 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: