Results for “planning”

Use when planning an IROS project timeline from venue fit through the spring paper deadline, the separate video deadline, the summer review silence, the June notification, the July camera-ready, IEEE Xplore publication, registration, and presentation, with backward-planning offsets for a real-robot paper on the fall IEEE/RSJ calendar.

Use when planning an EACL project timeline through ACL Rolling Review, covering the single viable ARR cycle with no fallback, backward planning from the one deadline, the rebuttal window, the commitment decision to EACL, notification, and camera-ready through ACL Anthology publication, plus re-routing since the next chance is another conference.

Plans features interactively, creates dependency-ordered tasks, and prepares Ralph for autonomous execution.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.

Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.

Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.

Refines task understanding through iterative questioning before executing, using the Joyride extension for human input.

Creates a concise, actionable plan for coding tasks by scanning context and producing a structured checklist.

Use when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.

Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.

Adaptively tutor, plan lessons, and provide practice exercises for any topic through active learning techniques.

Applies ITIL principles to design scalable, maintainable, and interoperable enterprise systems and solutions.

Creates detailed, bite-sized implementation plans from specs or requirements, with exact file paths, code, and TDD steps.

Analyze a codebase and generate a structured map of files relevant to a task before making changes.

Creates detailed, bite-sized implementation plans from specs or requirements, with file structure, task decomposition, and TDD steps.

Anchors work at the current moment and places events as spatial distances ahead or behind to improve temporal reasoning.

Trigger: project task list, task decomposition, phase planning, master orchestration, delivery governance. Scope: Project sequencing, task checklist creation, operating governance. Boundary: Excludes tactical code debugging.

Deep Confidence Harness — a thinking, planning, and execution framework that forces structured reasoning before acting. Combines Monte Carlo scenario analysis, calibrated confidence, multi-perspective debate, and optimal path planning. Use before any complex decision, build, or task. Activates on: 'deep confidence', 'think before you act', 'plan first', 'Atlas mode', 'reason through this', 'what should I do', 'think this through', 'best approach', 'reason carefully', 'plan and execute'.

Archives phase directories from completed milestones into versioned archive folders, showing a dry-run summary and moving directories only after confirmation.

Draws a Tarot spread to inject randomness into decision-making when prompts are vague or multiple approaches are equally valid.

Convert Notion specs into implementation plans, tasks, and progress tracking with linked Notion pages.

Creates detailed, bite-sized implementation plans from specs or requirements, with exact file paths, code, and test commands for TDD workflows.

Adaptive tutoring that diagnoses the learner's level, sets a small objective, teaches with examples, and includes practice with feedback.

Consolidates auto-memory files in ~/.claude/projects by auditing, planning, and executing a 4-phase cleanup with user approval.

Adaptive tutoring that diagnoses the learner's level, sets a small objective, teaches with examples, and gives practice with feedback.

Use when planning an AAAI project timeline from topic selection through abstract, OpenReview submission, two-phase review, rebuttal, decision, camera-ready, registration, presentation, and public artifact release.

Interviews users relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree.

Manage issues, projects, and team workflows in Linear using the Linear MCP server for natural-language project management.

Convert Notion product specs into linked implementation plans, tasks, and progress tracking with structured workflows.

Writes an actionable markdown implementation plan to .hermes/plans/ without executing code, using bite-sized tasks, exact paths, and complete code examples.