SKILL PLAN · DETERMINISTIC

A small plan for a real job

Start with the minimum useful stack. Add nothing unless it has a clear responsibility in the run.

Task
Change planning
Agent
Codex
Priority
Balanced
Start over

Rules + reviewed metadata only. No LLM. Same inputs produce the same plan.

03 SKILLS · Install order

Your Skill Plan

Install and verify one role at a time. The plan never forces three Skills when fewer are enough.

Read the public task guide ↗
01Core execution

Native · Codex

improve-codebase-architecture

Maps files, dependencies, tests, and reference patterns.
Open profile and install guide ↗
Review permissions, limitations, and evidence
Agent fit
Native · Codex
Main limitation
Architecture quality depends on change history and domain context that may be incomplete.
First risk
Premature refactoring · Medium
Source
Pinned source · 885e2ca4
02Guardrail

Native · Codex

repo-intake-and-plan

Breaks the change into ordered, testable phases.
Open profile and install guide ↗
Review permissions, limitations, and evidence
Agent fit
Native · Codex
Main limitation
It does not create environments, download assets, execute commands, perform paper lookup, or write the final report.
First risk
Planning from incomplete repository evidence · Medium
Source
Pinned source · 3ab50525
03Evidence

Portable · Codex

build-evidence-map

Records alternatives, consequences, and the evidence behind the choice.
Open profile and install guide ↗
Review permissions, limitations, and evidence
Agent fit
Portable · Codex
Main limitation
Validation proves graph integrity, not source quality or inference correctness.
First risk
Sensitive excerpts in portable artifacts · High
Source
Pinned source · 318066d2

Combined permission budget

This is the union of declared permissions across the plan. Review each package before installation.

Review package instructions before installRead filesWrite documentsRun commandsNetwork access

Finish with evidence

Produce an implementation-ready plan that reflects the repository's real dependencies.

Planning does not authorize implementation; unresolved assumptions remain visible.

  1. 3-step acceptance check
  2. Every phase names its inputs, changed paths, and verification step.
  3. Dependencies and rollback boundaries are explicit.
  4. Rejected alternatives include a concrete reason.
  • Stop conditions
  • The plan assumes files or APIs that were not inspected.
  • Implementation begins before critical assumptions are resolved.
  • The proposed change has no testable completion condition.