Results for “planning”

Generates a step-by-step construction plan from a one-line objective, where each step is self-contained and executable by a fresh agent in a new session.

Defines scope, objectives, rules of engagement, threat model selection, and operational timelines for red team engagements before any offensive testing begins.

Team lead agent — sprint planning, standups, velocity, impediments, team health

Product orchestrator for Prodig Suites that guides product planning, routes work to specialists, and coordinates execution across the product lifecycle. Use when the user is shaping a digital product, deciding next steps, or needs help choosing the right Prodig specialist or workflow. Triggers: 'prodig', 'digital product', 'product idea', 'product planning', 'which product agent should I use', 'SaaS planning', 'course creation', 'template pack', 'productized service'.

Expert en cuisine et recettes (meal planning, cooking techniques, substitutions, nutrition, DZ cuisine)

Generate visual storyboards with AI image generation, covering shot types, camera angles, movement, continuity rules, and panel layout for video planning and pre-production.

Execute the implementation planning workflow using the plan template to generate design artifacts.

Analyzes BIM models for clash detection, quantity takeoff, and construction sequence planning

Use when planning a CSCW submission timeline end to end — the PACMHCI journal model, the retired fixed cycles versus the rolling 2027+ pathway, Revise-and-Resubmit rounds that span months, and back-planning so an acceptance lands before the conference-year presentation cutoff.

Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.

Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use PROACTIVELY when the user asks about market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics, or business strategy for pre-seed through Series A startups.

Model cap tables, dilution scenarios, and vesting schedules for startups. Use when planning fundraising, pricing options, or tracking equity.

Orchestrate a configurable, multi-member CLI planning council (Codex, Claude Code, Gemini, OpenCode, or custom) to produce independent implementation plans, anonymize and randomize them, then judge and merge into one final plan. Use when you need a robust, bias-resistant planning workflow, structured JSON outputs, retries, and failure handling across multiple CLI agents.

Use when you have a spec or requirements for a multi-step task, before touching code. Writes comprehensive implementation plans.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

Plans a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on the issue tracker, resolved one at a time. Use when the user has a large ambiguous goal and wants the route charted.

Spawns GLM-5 powered teammates with thinking mode for coding, review, testing, planning, and research tasks.

Use this skill whenever a developer wants to turn an idea into a complete, production-ready, end-to-end system plan BEFORE writing any code. Trigger on 'plan this system', 'design the architecture for', 'help me blueprint', 'deep plan for X', 'break this idea into components', 'expand into action points', 'full implementation plan', or when the user pastes a project idea wanting architecture, components, pipelines, and file-level execution mapped out. Casual phrasing also triggers: 'help me think this through end-to-end', 'plan before coding'. Also covers living-workspace patterns: self-improving knowledge bases, reflection loops with auditor agents, four-agent teams, schema-as-code, wiki health scoring. **Resume triggers**: 'where did we leave off', 'continue this plan', 'resume my blueprint' - rehydrates state from disk via SESSION.md/NEXT.md/decisions/. Web research is mandatory every invocation.

Plan a chunk of work too big for one agent session by putting it on a shared whiteboard — a map of investigation tickets on GitHub Issues — working them until nothing is left to decide, then snapshotting the board into a handoff artifact. Tickets needing nobody are worked back-to-back; the session stops when the human is the blocker. Use only when the user explicitly invokes whiteboard or asks to draw, work, run, or snapshot a whiteboard/map — not for ordinary planning requests.

Use to forecast support contact volume and calculate staffing requirements for voice, chat, or async channels. Trigger for "how many agents do we need", "forecast our ticket volume", "Erlang C", workforce management or WFM planning, service level and occupancy targets, shrinkage, headcount planning for support, or when a staffing model keeps missing its service level.

Orchestrates a multi-agent build session, acting as manager to cut goals into units, spawn implementer and tester subagents, and run test-and-review loops with anti-thrash guardrails.

Run a bounded cross-platform landscape scan before planning or implementation. Use when the real job is researching what exists, how people work around it, which solutions repeat, or how platform/tooling patterns map before deciding what to build. Produce reusable `.survey/{slug}/` artifacts, validate the artifact contract, and route planning or execution outward only after the survey is done.

Clawdex — dual-engine coding agent. Claude Code (reasoning + planning) + OpenAI Codex (fast execution) + Browser Use boxes (web research) + Upstash compute boxes (isolated sandboxes).

Design a spaced retrieval schedule for any topic list and timeline. Use when planning units, term sequences, or revision programmes.

Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.

`analysis-agent`/`task-agent`/`review-agent`: discover source of truth, candidate owner, and change surface before planning; hand known candidates to impact inspection.

Use this when building or planning a Python command-line tool, command surface, argument model, package entrypoint, or automation-oriented CLI workflow.

Spawns GLM-5 powered teammates with native thinking mode for coding, review, testing, planning, and research tasks.

Analyse text complexity across quantitative, qualitative, and reader-task dimensions with scaffolding recommendations. Use when selecting texts, assessing readability, or planning reading support.

Coordinates UDL and differentiation tools through a universal-first hierarchy: barrier removal before targeted differentiation before individualised accommodation. Use when planning accessible learning.