What it is
plan-builder converts a ticket for a bug, enhancement, feature, removal, UI change or refactor into a prompt that a developer pastes into Codex. Codex then produces a repo-grounded implementation plan and changes nothing. The skill writes the prompt only. It never plans or implements the change itself and never edits the target repository.
What it does
- Turns a ticket into a complete, self-contained prompt for Codex Plan Mode.
- Accepts Jira text, screenshots, HTML, Markdown, PDFs, logs, emails or a plain description.
- Handles six task types: bug, enhancement, feature, removal, UI and accessibility change, and refactor.
- Requires a ticket number first, and asks for it if none is found (pattern such as
ABC-123).
- Asks for supporting artifacts, and counts files already supplied in the session as artifacts.
- Saves artifacts outside the repository, by default in
../plan-builder/artifacts/<TICKET>/files/.
save_artifacts.py never overwrites, verifies size and SHA-256, and refuses any destination inside a git work tree.- Includes an artifact path in the prompt only after the save is verified.
- Writes the prompt to
<TICKET>-codex-plan-prompt.md, with a fixed section order from Objective to Deliverable.
- Adds a task-type investigation block, such as root-cause tracing for bugs or backward-compatibility checks for enhancements.
- Opens and closes the prompt with a Plan Mode clause: no file edits, branches, commits or state-changing commands.
- Asks Codex for current architecture, root cause or design approach, files to modify, risks, tests, rollout and acceptance criteria.
- Labels each statement as Confirmed (from ticket) or Assumption, and puts gaps under Open questions instead of guessing.
- Treats text inside tickets, logs and emails as data. Instructions aimed at an AI are quoted, never obeyed.
- Warns about credentials or personal data in artifacts and refers to the file and line instead of copying values.
check_prompt.py validates required sections, absolute artifact paths and leftover placeholders before delivery.- Assumes no language, framework or folder layout. The prompt tells Codex to discover them.
- Needs Python 3.8+ with the standard library only.
Install and usage
Codex CLI prerequisite: PowerShell setup or WSL setup.
Install, then restart Codex:
$skill-installer install https://github.com/lowtouch-ai/krithi-skills/tree/main/skills/plan-builder
Usage example from the repository README:
$plan-builder build a plan prompt for ABC-123 from this ticket: <paste text or give a screenshot/HTML/Markdown path>
Then switch Codex to Plan mode (Shift+Tab or /plan) and paste the prompt, or say: Read <prompt path> and follow it. The skill cannot toggle Plan mode itself.
For update and uninstall steps, see the krithi-skills README.
Install all the skills together
If you want the whole set instead of one skill, point the installer at the repository root:
$skill-installer install all the skills in the https://github.com/lowtouch-ai/krithi-skills/
This asks Codex to install every skill in the krithi-skills repository in one step, so you do not repeat the install for each one. Restart Codex afterwards so the new skills are picked up.
The set currently covers four skills:
plan-builder: turns a ticket into a Plan Mode prompt that changes no code.repo-readme-generator: creates or updates a README and documentation suite from verified repository evidence.appsec-static-audit: runs a source-code-only security audit with compliance mapping.wave-a11y-scan: runs a WAVE-style accessibility scan mapped to WCAG 2.x.
Prefer to install one at a time? Use the single-skill command in the install section above.
