Skip to content
Skills Library
Programming · Research

plan-update

/plan-update

Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.

Repository
react ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.

Original author description

Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.

How it works

  1. Instructions
Original SKILL.md headings · 83 lines, 448 words
SKILL.md preview
---
name: plan-update
description: Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.
---

# Plan Update

Deep-research a topic across all compiler passes and update a plan document.

Arguments:
- $ARGUMENTS: `<plan-doc-path> <topic/question>`
  - Example: `compiler/docs/rust-port/rust-port-0001-babel-ast.md scope resolution strategy`
  - Example: `compiler/docs/rust-port/rust-port-architecture.md error handling patterns`

## Instructions

### Step 1: Read context

Read these files to understand the current state:
- The plan doc specified in $ARGUMENTS
- `compiler/docs/rust-port/rust-port-architecture.md` (architecture guide and port conventions)
- `compiler/packages/babel-plugin-react-compiler/docs/passes/README.md` (pass overview)

### Step 2: Launch parallel analysis agents

Launch **8 parallel Agent tool calls** using the `analyze-pass-impact` agent. Each agent analyzes one phase group. Pass each agent the topic from $ARGUMENTS and the list of pass doc files for its phase.

**Phase groups and their pass docs:**

1. **Lowering & SSA** (passes 01-03):
   `01-lower.md`, `02-enterSSA.md`, `03-eliminateRedundantPhi.md`

2. **Optimization & Types** (passes 04-06):
   `04-constantPropagation.md`, `05-deadCodeElimination.md`, `06-inferTypes.md`

3. **Function & Effect Analysis** (passes 07-09):
   `07-analyseFunctions.md`, `08-inferMutationAliasingEffects.md`, `09-inferMutationAliasingRanges.md`

4. **Reactivity & Scope Variables** (passes 10-14):
   `10-inferReactivePlaces.md`, `11-inferReactiveScopeVariables.md`, `12-rewriteInstructionKindsBasedOnReassignment.md`, `13-alignMethodCallScopes.md`, `14-alignObjectMethodScopes.md`

5. **Scope Alignment & Terminals** (passes 15-20):
   `15-alignReactiveScopesToBlockScopesHIR.md`, `16-mergeOverlappingReactiveScopesHIR.md`, `17-buildReactiveScopeTerminalsHIR.md`, `18-flattenReactiveLoopsHIR.md`, `19-flattenScopesWithHooksOrUseHIR.md`, `20-propagateScopeDependenciesHIR.md`

6. **Reactive Function & Transforms** (passes 21-30):
   `21-buildReactiveFunction.md`, `22-pruneUnusedLabels.md`, `23-pruneNonEscapingScopes.md`, `24-pruneNonReactiveDependencies.md`, `25-pruneUnusedScopes.md`, `26-mergeReactiveScopesThatInvalidateTogether.md`, `27-pruneAlwaysInvalidatingScopes.md`, `28-propagateEarlyReturns.md`, `29-promoteUsedTemporaries.md`, `30-renameVariables.md`

7. **Codegen & Optimization** (passes 31, 34-38):
   `31-codegenReactiveFunction.md`, `34-optimizePropsMethodCalls.md`, `35-optimizeForSSR.md`, `36-outlineJSX.md`, `37-outlineFunctions.md`, `38-memoizeFbtAndMacroOperandsInSameScope.md`

8. **Validation Passes** (passes 39-55):
   `39-validateContextVariableLValues.md`, `40-validateUseMemo.md`, `41-validateHooksUsage.md`, `42-validateNoCapitalizedCalls.md`, `43-validateLocalsNotReassignedAfterRender.md`, `44-validateNoSetStateInRender.md`, `45-validateNoDerivedComputationsInEffects.md`, `46-validateNoSetStateInEffects.md`, `47-validateNoJSXInTryStatement.md`, `48-validateNoImpureValuesInRender.md`, `49-validateNoRefAccessInRender.md`, `50-validateNoFreezingKnownMutableFunctions.md`, `51-validateExhaustiveDependencies.md`, `53-validatePreservedManualMemoization.md`, `54-validateStaticComponents.md`, `55-validateSourceLocations.md`

Each agent prompt should be:
```
Analyze how the topic "<topic>" affects the following compiler passes.

Read each pass's documentation in compiler/packages/babel-plugin-react-compiler/docs/passes/ and its implementation source. Also read compiler/docs/rust-port/rust-port-architecture.md for port conventions.

Pass docs to analyze: <list of pass doc filenames>

For each pass, report:
- Pass name and purpose (1 line)
- Impact: "none", "minor" (mechanical changes only), "moderate" (logic changes), or "significant" (redesign needed)
- If impact is not "none": specific details of what changes are needed
- Key code locations in the implementation (file:line references)

Be thorough but concise. Focus on concrete impacts, not speculation.
```

### Step 3: Consolidate and update

After all agents complete:
1. Merge their findings into a coherent analysis
2. Group by impact level (significant > moderate > minor > none)
3. Update the plan document. The final state should reflect the latest findings and understanding:
   - Update the plan document in-place to remove outdated content and describe the latest understanding. 
   - KEEP any existing content that is still relevant
   - REMOVE outdated or now-irrelevant content
   - Per-pass impact summary table (updated in place, ie update each section based on new findings)
   - Detailed notes for passes with moderate+ impact
   - Updated "Current status" or "Remaining Work" section if applicable

### Step 4: Show summary

Show the user a brief summary of findings: how many passes are affected at each level, and the key insights.

Versions

RepositoryScoreLicence
This page · facebook/react100MIT
ardallie/ace-classic100MIT
ardallie/ace-classic100MIT
thonymg/skills90MIT

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 6bc13c7fa1b4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100compiler-commit
    Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
  • 100researching-codebases
    Use when answering complex questions about a codebase that require exploring multiple areas or understanding how components connect - coordinates parallel sub-agents to locate, analyze, and synthesize findings
  • 90compiler-verify
    Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
  • 90reference-compiler-cli
    Explains the mental model and architecture of the code under `packages/compiler-cli`. You MUST use this skill any time you plan to work with code in `packages/compiler-cli`
  • 100execute-plan
    Implements an existing plan entirely in the main session, verifying each phase, updating progress and following the project's commit policy. Use to start, continue or resume a plan inline without subagents. Not for phase delegation (execute-plan-with-subagents), planning…
  • 90build-phase
    Build a specific phase by number. Spawns Builder to implement the approved phase plan. Phase 1 quality gates (PostToolUse, Stop hooks) fire automatically on Builder. Use when you're ready to implement an approved phase plan. Triggers on: '/build-phase', 'build phase', 'implement…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.