Results for “phase-plan”

Develops milestone-based project descriptions for Research, Prototype, and follow-on production Other Transactions, including objectives, phases, go/no-go structures, transition planning, and cost-analysis handoffs.

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

Plans and executes product launches with phased channel strategies. Use when the user requests 'product launch', 'GTM', 'go-to-market', 'Product Hunt', 'beta launch', 'early access', or 'launch checklist'.

Audit a Supabase/Postgres project for Row-Level Security and access-control gaps, then produce a phased remediation plan. Use when "RLS", "is my Supabase secure", "anyone can read my data", "lock down my tables". App-layer session/route gates → audit-auth-flows.

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.

Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts.

Audit a site for answer-engine / GEO citation readiness (ChatGPT, Perplexity, AI Overviews), then a phased plan. Use when "AEO", "GEO", "show up in ChatGPT/Perplexity", "AI search visibility", "llms.txt", or "am I blocking AI crawlers". Classic SEO meta/sitemap → enhance-web-seo.

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

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.

Creates a pull request from completed phase work, generates a rich PR body from planning artifacts, optionally runs code review, and prepares for merge.

Audit a codebase for silent failures, swallowed exceptions, and observability gaps across Sentry and Langfuse, then produce a phased fix plan. Use when the user says "errors aren't showing in Sentry", "things fail silently", "empty catch blocks", "add error handling", "check my Langfuse tracing", or is hardening.

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.

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.

Automatically detects project state and runs an 8-phase pipeline to plan, build, test, lint, fix bugs, and document code across multiple AI coding agents.

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 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.

This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'GTM plan,' 'launch checklist,' or 'launch momentum.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

Composite skill — safely refactor a module end-to-end with sequencing, parallel implementation, post-refactor cleanup, and rationale capture. Chains refactor-plan (phased plan + rollback) → three-man-team (architect/builder/reviewer in parallel) → fix-the-suite post-refactor → adr-write → docs-sync. Use for non-trivial refactors that need both careful sequencing and durable record.

Plans, builds, and deploys a complete Ethereum dApp using a three-phase build system with local fork, testnet, and production stages, plus a secret safety protocol and ERC-8004/x402 commerce flow.

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.

Systematic strategic planning framework for philosophy and interdisciplinary academic papers targeting preprint platforms (PhilArchive, arXiv, PhilSci-Archive). Use when users want to: (1) plan a paper on a specific topic, (2) identify research gaps and assess originality, (3) develop optimized paper outlines, (4) prepare for preprint submission, or (5) understand platform requirements and writing standards. Triggered by phrases like 'plan a paper on,' 'help me design a paper about,' 'identify research gaps in,' 'is this idea original,' or when users need structured research planning. The skill guides through three phases: Platform Analysis (identifying target venue and studying sample papers), Theoretical Framework (AI-driven literature search and gap identification), and Outline Optimization (structured design with reviewer-perspective self-assessment). Each phase includes quality evaluation standards and validation checkpoints. Output: optimized detailed outline ready for systematic writing (use with acade

Use this skill whenever a user wants to create a presentation outline, slide deck structure, storyboard slides, or plan a deck for any context (talk, boardroom, email report). Also use when the user mentions "help me structure my presentation", "slide outline", "storyboard my deck", "presentation flow", "plan my slides", "key message for my deck", "pyramid principle for slides", "what slides should I include", or "help me tell a story with slides". This skill walks through a complete, interactive process in two phases: Phase 1 (setup → key message → storyboard) saves a slide-outline.md; Phase 2 (interactive per-slide copy drafting → polish) saves a slide-copy.md that is linked from slide-outline.md. Trigger even when the user only mentions a vague intent like "I need to present X to my team" or "help me put together a board deck".

Structure the first 90 days of a VP or CPO transition as a diagnostic process, not an execution sprint, using a three-phase playbook to build evidence before making decisions.

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

Audit a codebase, UI, or copy for machine-generated tells across prose, visual/UI, code, and structure/IA, then produce a phased de-slop burndown. Use when the user says "feels AI-generated", "looks like AI slop", "reads like ChatGPT", "feels generic/soulless", or wants an authenticity/voice pass before launch.

GitHub Spec-Kit integration for constitution-based spec-driven development. 7-phase workflow (constitution, specify, clarify, plan, tasks, analyze, implement). Use when working with spec-kit CLI, .specify/ directories, or creating specifications with constitution-driven development. Triggered by "spec-kit", "speckit", "constitution", "specify", references to .specify/ directory, or spec-kit commands.

Use to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal window, notification, and the open-access camera-ready, adapting to whether the edition is a standalone ECAI (FAIA/PAIS) or the joint IJCAI-ECAI 2026.

Use when planning an ICLR project timeline from topic selection through OpenReview submission, discussion, revision, decision, camera-ready, poster, video, and public artifact release. Use when sequencing milestones against the current cycle's OpenReview deadlines, budgeting time for the long public discussion phase, or assigning owners for anonymity audits and reviewer-verifiable evidence paths.

Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).

VS-Enhanced Quantitative Design Consultant with Materials & Sampling Enhanced VS 3-Phase process: Avoids obvious experimental designs, proposes context-optimal quantitative strategies Absorbed C4 (Experimental Materials Developer) and D1 (Sampling Strategy Advisor) capabilities Use when: selecting quantitative research design, planning experimental/survey methodology, power analysis, developing materials, sampling Triggers: RCT, quasi-experimental, experimental design, survey design, power analysis, sample size, factorial design, materials, stimuli, sampling strategy

VS-Enhanced Qualitative Design Consultant with Ethnography & Action Research Enhanced VS 3-Phase process: Avoids overused phenomenology, proposes context-optimal qualitative strategies Absorbed H1 (Ethnographic Research Advisor) and H2 (Action Research Facilitator) capabilities Use when: selecting qualitative research design, planning phenomenology/grounded theory/case study/ethnography/action research Triggers: phenomenology, 현상학, grounded theory, 근거이론, case study, 사례연구, narrative inquiry, ethnography, 민족지, action research, 실행연구, qualitative design

Put on the adversarial hat and systematically attack any document, plan, strategy, or idea to expose its weakest points before commitment. Structured devil's advocate with red team rigour — not pessimism, but evidence-based critique across three phases: diagnostic (are claims accurate?), creative (is the problem artificially constrained?), challenge (are solutions robust?). Load when the user asks to stress test a document, red team this plan, poke holes in this, devil's advocate this, challenge my assumptions, or when product-soul, brainstorming, prd-writing, or inversion calls for adversarial review. Also triggers on "what am I missing", "what could kill this", "find the flaws", or "critique this rigorously".

Use when delivery work needs structuring into epics — defining a new epic, refining or superseding an existing one, or decomposing a PRD's requirements into durable delivery structures that feed issue decomposition. Writes docs/product/epics/NN-<slug>.md (durable, id-stable, superseded-never-deleted), each epic tracing to the JTBD ids it serves and the PRD requirement IDs it bundles. In the A-Team pipeline this is a definition-phase output ("the Epics"). Do not use for full roadmap/portfolio planning across quarters (deliberately not ported), for delivery tickets or acceptance criteria (ticket-writer), or to create or revise jobs (jobs-to-be-done).

Use when asked to fix, build, refactor, review, verify, or release software and the work is non-trivial — including delivering a change request (issue, ticket, or request) from intake through planning, gates, implementation, review, verified PR, and authorized post-merge release. neckbeard routes the change through framing, discovery, design, implementation, review, verification, delivery, and learning — choosing the smallest *safe* intervention, proving it at the real delivery boundary, and leaving an inspectable evidence ledger. For change-request / issue-to-PR work, conditionally loads a 9-phase journey with gates, delivery packet, and lifecycle integration. Composes specialist catalog skills rather than replacing them. Not a persona, not a '10x developer' prompt, not a LOC-minimizer. The journey is not loaded for plain fixes, refactors, or reviews that lack an issue/ticket trajectory.