Results for “pr-plan”

Use when planning an ESEC/FSE project timeline from venue fit through paper registration, submission, the journal-style Major Revision round, artifact evaluation, PACMSE camera-ready, and presentation, with backward-planning offsets for an empirical-SE paper and honest handling of the single-annual-deadline cycle and cycle-hopping.

Displays comprehensive project statistics including phases, plans, requirements, git metrics, and timeline.

Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.

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 a CIKM project calendar across the May abstract/paper gates, June short-track gates, August notification and camera-ready, and the November conference, including the post-submission phase now live in the 2026 cycle, multi-track coordination, and fallback planning toward CIKM 2027 or sibling venues.

Builds, validates, schedules, and dynamically modifies DAG execution graphs. Decomposes problems into nodes with dependencies, performs topological sorting, detects cycles, resolves conflicts, and schedules wave-based parallel execution. Use when designing a DAG structure, validating dependencies, planning execution order, or modifying a DAG at runtime. Activate on "build DAG", "plan workflow", "DAG dependencies", "topological sort", "schedule execution", "modify DAG", "replan". NOT for executing DAGs (use dag-runtime), validating outputs (use dag-quality), or matching skills to nodes (use dag-skills-matcher).

Use when planning a KDD project calendar across the venue's two submission cycles per year, including cycle choice, abstract-then-paper deadline pairs a week apart, rebuttal capacity planning, the Resubmit-to-next-cycle loop, ADS evidence lead times, and ACM e-rights/TAPS camera-ready scheduling for SIGKDD.

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.

Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session

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.

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.

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

Provides a general standard operating procedure for handling requests related to as, mao, his, with steps, checks, and fallback plans.

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.

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.

Facilitates a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

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 includes practice with feedback.

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.

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

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

Review any business decision, plan, or strategy through the minimalist entrepreneur lens, providing a gut-check and simplification advice.

Diagnoses short video opening problems and generates actionable optimization plans based on content quality and hook strategies.

Use when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first development practices.

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

Implements a structured problem-solving algorithm that guides every response through observe, think, plan, build, execute, verify, and learn phases toward a defined ideal state.

Orchestrate the full MoonSpec lifecycle from a preselected single-story feature request or active feature directory through specification, planning, TDD task generation, artifact alignment, implementation, and final verification. Use when the user asks for an end-to-end MoonSpec run and the input has already been routed to one independently testable story, or when Codex needs to coordinate `moonspec-specify`, `moonspec-plan`, `moonspec-tasks`, `moonspec-align`, `moonspec-implement`, and `moonspec-verify` without manual analyze/remediation prompts.

Use this skill for dependency upgrades, SDK migrations, breaking changes, compatibility plans, rollback. Trigger when the task involves programming work related to Deprecation Migration, production implementation, audits, debugging, strategy, or validation.

Surface and clarify unknowns before prompting, log deviations during implementation, and verify understanding after, using HTML artifacts that pair prompts with outputs.

Maps support capabilities, plans cross-training, and sizes multi-skilling against real proficiency and routing cost.

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.

Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents.

Breaks a topic into a sequence of adaptive learning articles, adjusting depth and pace based on user feedback from the previous lesson.

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