What problem does it solve?
Teams keep implementation plans in many formats—OpenSpec changes, spec-kit specs, GitHub or GitLab issues with checklists, generic task lists, or free-form notes—but ralphex only executes plans written in its own strict markdown structure. Manually rewriting these sources into the required docs/plans/YYYYMMDD-slug.md format with proper Task sections and checkboxes is tedious and error-prone.
Core Features & Use Cases
- Multi-format source resolution: Accepts URLs, issue references (
#N, owner/repo#N), file paths, directories, or bare names, fetching content via gh, glab, or direct file reads.
- Format detection and mapping: Classifies sources as OpenSpec, spec-kit, issue-with-checklist, generic task-list, or free-form, then maps each into ralphex's required sections (Overview, Context, Implementation Steps with
### Task N: headers).
- Guarded drafting workflow: Asks clarifying questions before drafting, runs a revdiff review loop (with in-chat fallback), confirms the output slug, and never silently overwrites existing plan files.
- Use Case: You have a GitHub issue with a 12-item checklist describing a feature. Run the skill with the issue number to produce a ready-to-execute ralphex plan grouped into Tasks with test checkboxes and a final acceptance-criteria verification task.
Quick Start
Ask the assistant to adopt the plan from GitHub issue #42 into a ralphex plan file under docs/plans.