r13v

11 mods across 1 repository, 2 stars between them.

creator-vibe

01

r13v/pi-feature-dev

Skill Claude CodeCodex

Use first for creative work—technical or everyday—when a brief is incomplete or intent is implicit and success depends on taste, voice, feeling, or human experience. Also trigger when literal compliance may lose the point. Do not wait for explicit creative wording. Skip factual lookup, mechanical or exact tasks, and…

2 14d ago A 69 tokens original MIT

feature-dev

02

r13v/pi-feature-dev

Skill Claude CodeCodex

Structured feature development workflow for coding assistants. Use for non-trivial feature work requiring codebase exploration, clarification, architecture trade-offs, implementation approval, review, and final summary.

2 14d ago A 38 tokens original MIT

final-check

03

r13v/pi-feature-dev

Skill Claude CodeCodex

What else have we missed? Is there anything we need to check or fix? Use when the user invokes $final-check.

2 14d ago A 28 tokens original MIT

grill

04

r13v/pi-feature-dev

Skill Claude CodeCodex

Relentlessly stress-test an idea, plan, requirement, architecture, or domain model through dependency-aware interview rounds. Use when the user asks to be grilled, challenged, interviewed, or pushed toward shared understanding; when assumptions and decision branches must be exhausted before action; or when domain…

2 14d ago A 78 tokens original MIT

i-have-adhd

05

r13v/pi-feature-dev

Skill Claude CodeCodex

Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".

2 14d ago C 62 tokens copy · 98% MIT

plan-exec

06

r13v/pi-feature-dev

Skill Claude CodeCodex

Execute implementation plan files task by task with isolated workers, task commits, internal reviews, finalize, and a portable run summary.

2 14d ago A 29 tokens original MIT

plan-make

07

r13v/pi-feature-dev

Skill Claude CodeCodex

Create structured implementation plans in docs/plans/ for feature work, bug fixes, refactors, migrations, or unclear implementation requests. Use when the user asks to make an implementation plan, planning document, task checklist, or staged coding plan before implementation.

2 14d ago A 54 tokens original MIT

plan-review

08

r13v/pi-feature-dev

Skill Claude CodeCodex

Review implementation plans against the actual repository before execution, combining plan-quality checks with an evidence-backed technical pre-mortem and a PASS / REVISE / BLOCK verdict. Use after a plan is created or when the user asks to validate a plan for correctness, scope, over-engineering, missing tests…

2 14d ago A 123 tokens original MIT

prototype

09

r13v/pi-feature-dev

Skill Claude CodeCodex

Build disposable code to answer one product or engineering design question. Use when the user wants to validate logic, state transitions, a data model, or API behavior, or compare structurally different UI directions before production implementation. Adapt to the current repository and agent environment. Do not…

2 14d ago A 79 tokens original MIT

ste

10

r13v/pi-feature-dev

Skill Claude CodeCodex

Draft, rewrite, and review clear, unambiguous English with ASD-STE100 Simplified Technical English Issue 9 principles. Use for READMEs, runbooks, procedures, safety instructions, API and tool documentation, prompts, agent instructions, UI and error messages, status and incident reports, release notes, support text…

2 14d ago A 129 tokens original MIT

visual-recap

11

r13v/pi-feature-dev

Skill Claude CodeCodex

Create evidence-backed visual recaps of planned or completed non-trivial changes. Use after planning or completing non-trivial work when a visual review aid would reduce review effort, or when the user asks for a visual recap, visual plan, change map, system overview, architecture impact, before/after view, or…

2 14d ago A 96 tokens original MIT