init-rpm

Files (3)

• SKILL.md
• detect.sh · scripts/
• repair.sh · scripts/

SKILL.md (first lines)

# /init-rpm — Full Instructions

Project setup and verification. First run creates rpm context for a
project. Repeat runs verify that an existing rpm setup matches the
latest expected layout and apply safe migrations.

Run once per project, or run again after installing rpm in a new agent
runtime such as Codex. On repeat runs, do not re-ask first-run
project context questions unless a required canonical file is missing
and the answer cannot be inferred from existing files.
If `docs/rpm/context.md` already exists, read it and **augment** — do not
overwrite. Merge in missing sections only.

If any `docs/rpm/` content already exists, treat this as an rpm migration/update,
not a brand-new install. Preserve existing rpm files, create only missing
canonical files (`context.md`, `past/log.md`, `present/status.md`,
`future/tasks.org`, `future/done.org`, `reviews/`), and migrate legacy names
when present:

- `docs/rpm/FUTURE.org` or `docs/rpm/future/FUTURE.org` -> `docs/rpm/future/tasks.org`
- `docs/rpm/PRESENT.md` or `docs/rpm/present/PRESENT.md` -> `docs/rpm/present/status.md`
- `docs/rpm/RPM-LOG.md` or `docs/rpm/past/RPM-LOG.md` -> `docs/rpm/past/log.md`
- `docs/rpm/RPM.md` -> `docs/rpm/context.md`

Narrate as you go. At each phase, tell the user what's about to happen
in one short sentence before doing it — users should never be surprised
by what `/init-rpm` creates or writes.

## Phase 0: Introduce

Before running anything, detect whether this is a first run:

- If `docs/rpm/` does not exist, use the first-run introduction below.
- If any `docs/rpm/` content exists, this is a repeat run. Use the
  verification introduction below, then follow **Repeat-run
  verification mode**.

First-run wording (adapt freely):

```
## /init-rpm — rpm first-run setup

I'll set up rpm (Relentless Project Manager) for this project. Here's
what I'm about to do:

1. Detect the project — language, tests, existing docs
2. Ask 1–3 questions I can't answer from the codebase
3. Create `docs/rpm/` scaffolding (context, trackers, past/future/reviews)
4. Create an agent instructions file if one is missing
5. Ask once for runtime permissions if the active agent supports them
6. Summarize what was created

Starting with detection.
```

Do NOT wait for confirmation — this is informative, not gating.
Proceed immediately to Phase 1.

Repeat-run wording (adapt freely):

```
## /init-rpm — rpm setup verification

I found existing rpm state. I won't re-bootstrap this project or ask
first-run questions. I'll verify it against the latest rpm layout,
apply safe migrations for missing canonical files or legacy names, and
ask before changing agent guidance.

Starting with verification.
```

Do NOT wait for confirmation — this is informative, not gating.

### Repeat-run verification mode

Run this mode when `docs/rpm/` exists, `docs/rpm/context.md` exists,
or any legacy rpm file exists (`docs/rpm/RPM.md`,
`docs/rpm/FUTURE.org`, `docs/rpm/PRESENT.md`,
`docs/rpm/RPM-LOG.md`).

1. **Scan current state.** Run the Phase 1 detector and read existing
   `docs/rpm/context.md`, `docs/rpm/present/status.md`,
   `docs/rpm/future/tasks.org`, `docs/rpm/future/done.org`, and
   `docs/rpm/past/log.md` only when they exist.
2. **Verify canonical rpm files.** Create only missing canonical
   files/directories:
   - `docs/rpm/context.md`
   - `docs/rpm/past/log.md`
   - `docs/rpm/present/status.md`
   - `docs/rpm/future/tasks.org`
   - `docs/rpm/future/done.org`
   - `docs/rpm/reviews/`
3. **Apply safe legacy migrations.** Move legacy names listed above
   to the canonical paths only when the canonical target is missing.
   If both old and new paths exist, do not overwrite; report the old
   path as leftover legacy state.
4. **Repair stale configs.** Run the unified repair pass — see
   the **Phase 4a: Repair stale configs** section below. It brings
   `.gitignore` and `AGENTS.md` in line with the current rpm layout
   (wildcard ignore rule + `# include:` directive for Codex).
5. **Verify agent guidance layout.** If `CLAUDE.md` exists and
   `AGENTS.md` is missing or `CLAUDE.md` appears to contain general
   project guidance, ask the Claude guidance migration question from
   Phase 4. Do not move guidance without confirmation.
6. **Verify runtime-specific permissions.** Run Phase 6 checks, but
   only apply permission changes for runtimes that support them.
7. **Verify current-session activation.** Ensure
   `docs/rpm/~rpm-session-start` exists for the current session when
   the active runtime uses rpm lifecycle hooks.
8. **Summarize and stop.** Print:

   ```
   ## /init-rpm verification complete

   Verified: {list}
   Created: {list or "nothing"}
   Migrated: {list or "nothing"}
   Repaired: {list or "nothing"}
   Needs attention: {list or "nothing"}

From dppdppd/rpm, MIT.

More from dppdppd/rpm