Results for “pr-plan”

Turns a raw idea into four linked planning files through a five-phase pipeline: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with kill criteria.

Get Shit Done - Full project planning and execution workflow. Handles project initialization with deep context gathering, automated research, roadmap creation, phase planning, and execution with verification.

Clerk Billing for subscription management - render Clerk's PricingTable and in-app checkout drawer, configure subscription plans, seat-limit plans for B2B, feature entitlements with has(), and billing webhooks. Use for SaaS monetization, plan gating, checkout flows, trials, invoicing, and subscription lifecycle management.

Use when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria. Produces a research execution plan organized in canonical research phases — collection, preparation, analysis, robustness, writing, submission.

Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.

Designs analytics architecture, plans events, defines KPIs, sets attribution boundaries, and reviews instrumentation across product and growth.

Create a practical onboarding plan for a new team member with outcomes, first-week structure, stakeholder introductions, learning path, and manager check-ins.

Create and manage budgets with variance analysis and departmental allocation. Use when the user requests budget planning or provides relevant inputs for this workflow.

Drafts FDA product recall plans compliant with 21 CFR Part 7, covering Recall Committee governance, health hazard evaluation, recall classification, notification protocols, effectiveness checks, product disposition, and termination procedures. Use when developing recall SOPs, updating recall procedures, drafting recall readiness plans, or preparing FDA-regulated product recall documentation.

Routing-first visual approval gate for AI agent plans, markdown specs, and diffs. Use when a human needs to review a concrete plan before execution, inspect a targeted diff in a browser, mark up a spec/PRD/architecture note, or set up the review loop on Claude Code, Gemini CLI, Codex CLI, or OpenCode. Route planning/spec creation to `task-planning` or `ralph`, broad PR-policy review to `code-review`, rendered-UI critique to `agentation`, and fresh-session browser verification to `browser-harness`.

Prepare GPT-pro-ready proof planning or diagnosis bundles from a user's idea, packaging claims, sources, givens, and open questions for review without solving gaps locally.

Use when a research implementation plan exists in docs/superpapers/plans/ and the user is ready to execute it — collecting data, running analysis, producing outputs, writing the paper. Orchestrates task execution with replication-driven verification and two-stage review at phase boundaries.

Breaks complex problems into iterative reasoning steps with revision, branching, and dynamic scope adjustment for multi-stage analysis and planning.

Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test code — use tdd to implement behavior test-first. Does not refine existing plans — use iterative-plan-review. Does not review code quality, security, or style — use code-review for full code review. Does not evaluate architectural testability or structural coupling — use architectural-analysis for architectural assessment.

Creates and manages Product Requirements Documents (PRDs) with structured user stories, acceptance criteria, and progress tracking for feature planning.

Plan tailored engagement for a specific stakeholder before critical conversations, milestones, or relationship repairs.

Generates detailed lesson plans for MBot robotics and programming courses, including structured sections and simulated teacher-student dialogues.

Map stakeholders on a power/interest grid and generate a tailored communication plan for each group.

Analyzes AI disruption pressure across a business, maps competitive exposure, and produces a 90-day defensive action plan.

Takes an approved plan from docs/plans/ and drives it to an open PR. Implements it by milestones, commits per milestone in the repo's style, and opens the PR against the repo's base branch. Use whenever the user approves a plan, says "ship it", "go", "start", "implement it", "do it", or asks to open a PR for already-planned work — or in Spanish "dale", "arrancá", "implementalo", "hacelo".

Plan and implement UI

Plan a field event, dinner, or conference presence that actually produces pipeline, not just badges scanned. It builds the right guest list, designs a draw worth showing up for, plans the on-site motion so conversations happen, and writes the follow-up that converts, because the pipeline is made after the event, not at it. Built for B2B field marketing and sales teams, customizable to your CRM and your event motion. Trigger on "plan a field event", "customer dinner plan", "conference presence", "how do I get pipeline from this event", "event guest list", "event follow-up plan", or any field-event or in-person pipeline request.

Splits a body of context into a sequence of vertical-slice build phases where each phase is independently demonstrable to a real user and each builds on the previous. Use when the user wants to plan, sequence, phase, slice, break down, or order the build of a feature, capability, system, or initiative, and produces a plain-language phased build outline. Does not produce implementation detail — use plan-implementation. Does not specify behavior that has not been decided — use plan-a-feature. Does not perform gap analysis between two artifacts — use gap-analysis. Does not break a plan into independently-grabbable work items — use plan-work-items.

Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not plan to local files only — use plan-a-feature. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features to Confluence — use project-documentation-to-confluence.

Drafts a Spill Prevention, Control, and Countermeasure (SPCC) Plan compliant with 40 CFR Part 112 under the Clean Water Act. Covers facility characterization, oil storage inventory, secondary containment, prevention measures, response procedures, training, and PE certification language. Use when drafting SPCC plans, oil spill prevention documents, or EPA compliance submissions.

Coordinates sprint planning, delivery tracking, experiment management, knowledge management, and changelog governance across project management workflows.

Create and manage persistent markdown planning files for structured task execution. Use when the user asks to "create a plan", "track progress", "start a research project", or when a task requires more than 5 tool calls and needs structured phase tracking to stay focused and avoid goal drift.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Rebuilds working context after a session clear by reading git history, plans, and beads issue state, then produces a visible briefing.

Interviews the user in depth about a plan, probing technical implementation, UI/UX, risks, tradeoffs, and missing decisions before writing or refining a spec.

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Writes concise weekly progress, plans, and problems updates for teams, pulling context from Slack, Drive, email, and calendar when available.

Audit a project for destructive-operation and migration safety gaps, then produce a phased safeguard plan. Use when "is my migration safe", "could I lose data", "my agent might delete prod", or "safe schema changes". Restore drills and RPO/RTO belong to plan-backup-dr. Source transforms → audit-codemod-safety.

Manage issues, projects, and team workflows in Linear with structured workflows for sprint planning, bug triage, and release management.

Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.

Generate three alternative OKR sets for a team, aligned with company strategy, to spark strategic discussion and planning.