Results for “plan-review”

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.

Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.

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.

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

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.

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

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

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

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.

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 ICRA submission calendar end to end — the September paper deadline, the two video-attachment windows, winter review silence, late-January notification, March camera-ready, and the May/June conference — or when interleaving a fallback RA-L or IROS plan around the single annual ICRA shot.

Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.

Strategic planning with optional interview workflow

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

Strategic planning with optional interview workflow

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

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.

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

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.

P7 Senior Engineer mode — solution-driven execution under P8 supervision. Use when user says 'P7模式', '方案驱动', or when spawned as sub-task executor by P8. Produces: implementation plan + code + 3-question self-review, delivered via [P7-COMPLETION].

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.

P7 Senior Engineer mode — solution-driven execution under P8 supervision. Use when user says 'P7模式', '方案驱动', or when spawned as sub-task executor by P8. Produces: implementation plan + code + 3-question self-review, delivered via [P7-COMPLETION].

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.

Manage, inventory, standardize, migrate, and test reusable Codex skills for the MetaSkill repository. Use when Codex needs to inspect local skills, convert a personal workflow into a public skill candidate, normalize skill folder shape, plan skill promotion, or decide whether a skill belongs in skill-management, publication-review, or skill-examples.

Use when planning a CoRL submission cycle end to end — the late-May abstract and paper deadlines, the summer review window, first-round rejection risk, the August one-page rebuttal and discussion period, autumn decisions, the October PMLR camera-ready, and the November conference — including what to do between milestones.

Use when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.

Use when planning or sequencing an ICML manuscript workflow end to end - from topic selection and drafting through OpenReview submission, double-blind review, author response, camera-ready, PMLR publication, public original-submission release, and rerouting decisions. Use when you need the next ICML skill, the official page to reopen, or the blocking gap for the current stage.

Creates or updates a repo's CLAUDE.md by exploring the code and adding the standard workflow sections (git/PR rules, changes that require human review, non-obvious context). Use whenever the user is starting in a new repo, says "set up the CLAUDE.md", "onboard this repo", "there's no CLAUDE.md here", or asks to complete or improve an existing CLAUDE.md — or in Spanish "armá el CLAUDE.md", "iniciá este repo", "falta el CLAUDE.md acá". Also run it before the first time `plan` runs in a repo that has no CLAUDE.md yet.