Results for “planning”

Coordinates a goal lifecycle: define, decompose, activate, track, and execute goals using a set of system skills that write markdown files.

Delivers changes incrementally by building in thin vertical slices, testing and verifying each piece before moving to the next.

Identify, assess, and mitigate project risks across technical, scope, dependency, and timeline categories using a structured register and escalation rules.

Transform text plans into interactive visual documents with diagrams, code snippets, and review surfaces for coding agents.

Guides a structured feature-development workflow: explore the codebase with subagents, draft a plan for approval, implement step by step, verify with parallel checks, and record conventions.

Imports external plan files into a GSD-structured project, detecting conflicts against existing roadmap, requirements, and locked decisions before writing a validated PLAN.md.

Captures ideas, tasks, or issues during a GSD session as structured todos for later work, enabling a thought-to-capture-to-continue flow without losing context.

Orchestrates building a new feature end-to-end by delegating research, planning, TDD implementation, review, and gated commit to specialized agents.

Turns a spec or requirements into a detailed, bite-sized implementation plan with exact file paths, code, and test steps for engineers with no codebase context.

Detects the current state of an Open-workspace project and advances to the next logical workflow step, from discussion through planning, execution, verification, and completion.

Checks project progress, summarizes recent work and what's ahead, then routes to the next action by executing an existing plan or creating a new one.

Creates detailed, step-by-step implementation plans from specs or requirements, with task decomposition, file structure, and test-driven development instructions.

Turns a rough request into working software via a governed build loop: align first, plan, then iterate one task at a time with deterministic backpressure and holdout-scenario judging.

Runs an interactive weekly review session to assess accomplishments against stated goals, identify missed items, and plan the next week with a structured report and accountability question.

Provides a framework for designing and implementing a company operating system, covering accountability charts, scorecards, meeting rhythms, issue resolution, and quarterly priorities.

Subjects every non-trivial decision to a fresh-context adversarial review before it stands, prioritizing correctness over speed for high-stakes or unfamiliar code.

Defines a gated Research-Plan-TDD-Review-Commit pipeline for orchestrating feature development, defect fixes, and refactoring tasks through composable phases and human approval gates.

Coordinates a squad of specialized agents for software development, routing tasks and managing context across requirements, planning, architecture, implementation, review, testing, and deployment phases.

Converts syllabi, past papers, or notes into a ranked study roadmap ordered by difficulty, with support for theory, numericals, MCQs, coding, and lab prep.

Turns a one-line objective into a step-by-step construction plan that any coding agent can execute cold, with each step containing a self-contained context brief.

Turns a one-line objective into a step-by-step construction plan any coding agent can execute cold, with each step containing a self-contained context brief.

Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).

Provides structured coaching for founders and first-time CEOs, covering archetype identification, delegation frameworks, energy management, calendar audits, leadership evolution, and blind spot identification.

Provides HR business partner guidance for organizational planning, hiring, performance management, talent reviews, and employee relations, with templates for role design, interview rubrics, onboarding plans, and communication.

Run a user story mapping workshop with adaptive questions and a structured map output, generating backbone activities, user tasks, and release slices for a workflow.

Collaboratively write multi-volume novels with structured commands for outlining, planning, drafting, writing, health-checking, and archiving, while maintaining world-building consistency across chapters.

Design user journeys and task flows for a product concept or MVP. Use when the team needs primary flows, branch conditions, edge cases, onboarding paths, and end-to-end user movement before screen planning or UI implementation.

Create implementation-ready engineering plans for WelineFramework. Use in Plan mode, or when the user requests detailed requirements, code modification points, task cards, test cases, acceptance criteria, risk and rollback design, or a handoff package for execution-oriented AI agents.

Turns a rough request into working software via a governed build loop: align first, plan, then iterate one task at a time with deterministic backpressure and holdout-scenario judging.

Automates privacy impact assessments including data flow mapping, risk scoring, GDPR/CCPA compliance checks, and remediation planning using the NIST Privacy Framework and ICO DPIA guidance.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Guide for translating code between programming languages. Use when converting code from one language to another, planning language migrations, understanding conversion challenges, asking about type mappings, idiom translations, or referencing pattern mappings. Covers APTV workflow, type systems, error handling, concurrency, and language-specific gotchas.

Use when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.

Use when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.

Use when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.

Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.