plan-one-shot

Original：🇺🇸 English

Translated

Create Antigravity-style implementation plans with strict review gates, line-item IDs, and no code changes until the user explicitly says Execute Plan.

1installs

Sourceishk-sftckz/exspecso

Added on2026-02-14

NPX Install

npx skill4agent add ishk-sftckz/exspecso plan-one-shot

SKILL.md Content

View Translation Comparison →

Plan One Shot

Replicate Antigravity plan-mode behavior using three artifacts and strict review gates.

Hard Rules

Before approval: plan only. No code edits, no mutating commands, no commits.

Always produce or update these artifacts together:

```
.exspecso/<plan-name>/task.md
```

.exspecso/<plan-name>/implementation_plan.md

```
.exspecso/<plan-name>/walkthrough.md
```
(stub only during planning)

Match plan depth to scope.
Block execution until user says exactly:
```
Execute Plan
```
.
Do not skip artifact generation even for short tasks.
After approval: execute strictly in
```
task.md
```
order and update statuses continuously.
For existing projects, preserve architecture, naming, folder layout, and dependency choices unless the user asks for a change.
Prefer minimal diff; do not introduce new abstractions/libraries unless justified by at least two concrete reuse points or a clear blocker.

Output Control Rules

Scope-fit depth: small tasks -> short plans; large tasks -> comprehensive plans.
No speculative engineering: avoid unrequested future-proofing.
No vague placeholders like "update logic"; describe exact changes.
Keep verification realistic and runnable in the current repository.
Prefer adapting existing modules over creating new ones.
Keep tool/process notes out of main workstream bullets unless they directly affect implementation steps.

Required Plan Structure

implementation_plan.md

must follow this order:

Title
One-line objective
```
## Proposed Changes
```
Workstreams

File blocks using this format:

#### [MODIFY] [path/to/file.ts](file:///absolute/path/to/file.ts)

#### [CREATE] [path/to/new-file.ts](file:///absolute/path/to/new-file.ts)

```
## Verification Plan
```

Use

---

between major workstreams.

Artifact Lifecycle

All artifacts for one plan must live under a single date-prefixed folder:

```
.exspecso/YYYY-MM-DD-<plan-name>/
```

<plan-name>

rules:

Lowercase.
Keep letters, numbers, and spaces before slug conversion.
Convert spaces/underscores to
```
-
```
.
Remove filler words when possible (
```
the
```
,
```
a
```
,
```
an
```
,
```
for
```
,
```
to
```
,
```
of
```
).
Keep first 3-6 meaningful words.
Max length 36.
Collapse repeated
```
-
```
and trim edges.

Replan Decision Gate

For every new request after plan creation, decide first:

```
Decision: Continue Current Plan
```
```
Decision: Create New Plan
```

Provide one short reason.

Create a new plan when objective/success criteria change materially, a new subsystem is introduced, architecture shifts significantly, or planned updates would rewrite roughly more than 40% of the current plan.

task.md Template

markdown

# <Task Name>

## Planning
- [/] Explore codebase and identify gaps
- [/] Write implementation plan

## Execution
- [ ] <work item>
- [ ] <work item>

## Verification
- [ ] <verification item>

Rules:

During planning, keep Planning items as
```
[/]
```
.
Keep Execution/Verification unchecked until execution starts.
Keep items concise and action-oriented.

walkthrough.md Planning Stub