ralphonce

Name: ralphonce
Author: sterlingcrispin

201stars18forks

How to install ralphonce?

sterlingcrispin/claude_slash_commands/ralphonce

$npx -y skills add sterlingcrispin/claude_slash_commands --skill ralphonce

Installs into the current project.

Summary

Work on a single highest-priority feature from current_ documents, test it, update docs, and commit

Files · 1

View on GitHub

SKILL.md

1	# Ralph Once - Single Feature Implementation Cycle
2
3	You are about to execute a focused, single-feature development cycle. Follow these steps precisely:
4
5	## Step 1: Read Current Documents
6
7	Find and read ALL files in the current project that start with `current_` (e.g., `current_PROGRESS.md`, `current_PRD.json`, or for example `current_SYSTEM-PLAN.md`, or any other `current_* files could be .txt , .json , .md or other). These contain the project roadmap, PRD, and progress tracking.
8
9	## Step 2: Identify the Highest Priority Feature
10
11	After reading all `current_*` documents, YOU decide which single feature has the highest priority. Consider:
12	- Dependencies (what must be built before other things can work)
13	- Foundation vs polish (infrastructure before features)
14	- Blocking issues (what's preventing progress)
15	- Stage progression (complete earlier stages before later ones)
16
17	Do NOT just pick the first item in a list. Use your judgment about what will provide the most value or unblock the most work.
18
19	Announce your choice and briefly explain WHY you chose it before proceeding.
20
21	## Step 3: Implement the Feature
22
23	Work on ONLY this single feature. Do not scope creep. Do not "also fix" other things. Stay focused.
24
25	## Step 4: Test the Feature
26
27	- If tests exist for this feature area, run them and ensure they pass
28	- If no tests exist, write appropriate tests for the feature you just implemented
29	- All tests must pass before proceeding
30
31	## Step 5: Update the PRD
32
33	Find the `current_*` document that serves as the PRD/plan (likely `current_PRD.md` or similar). Update it to reflect:
34	- Mark the completed item as done (change `"passes": false` to ` "passes": true]` if using that or change "done" to true)
35	- Note any design decisions made during implementation
36	- Update any sections that are now outdated
37
38	## Step 6: Append to Progress File
39
40	Find `current_PROGRESS.md` (or the equivalent progress journal tracking file). Append a new entry to the Session Log with:
41	- Today's date
42	- What feature was implemented
43	- Key implementation details
44	- Any issues encountered and how they were resolved
45	- What tests were added/run
46
47	## Step 7: Git Commit
48
49	Stage and commit all changes with a clear commit message describing the feature implemented.
50
51	Do NOT push unless explicitly asked.
52
53	---
54
55	## CRITICAL RULES
56
57	1. ONE FEATURE ONLY - Do not work on multiple features. Stop after completing one feature cycle.
58	2. TESTS REQUIRED - Do not skip testing. Either run existing tests or write new ones.
59	3. DOCUMENT EVERYTHING - The progress file is your memory between sessions. Be thorough.
60	4. COMMIT ATOMICALLY - Each /ralphonce invocation should result in exactly one focused commit.

People who liked this also viewed

6 picks

Type

find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 20262.6M27k
grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026633k182k
vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026573k29k
improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026522k182k
setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026454k182k
triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026424k182k

ralphonce

201stars18forks

View on GitHub

How to install ralphonce?

sterlingcrispin/claude_slash_commands/ralphonce

$npx -y skills add sterlingcrispin/claude_slash_commands --skill ralphonce

Installs into the current project.

Summary

Work on a single highest-priority feature from current_ documents, test it, update docs, and commit

Files · 1

View on GitHub

SKILL.md

1	# Ralph Once - Single Feature Implementation Cycle
2
3	You are about to execute a focused, single-feature development cycle. Follow these steps precisely:
4
5	## Step 1: Read Current Documents
6
7	Find and read ALL files in the current project that start with `current_` (e.g., `current_PROGRESS.md`, `current_PRD.json`, or for example `current_SYSTEM-PLAN.md`, or any other `current_* files could be .txt , .json , .md or other). These contain the project roadmap, PRD, and progress tracking.
8
9	## Step 2: Identify the Highest Priority Feature
10
11	After reading all `current_*` documents, YOU decide which single feature has the highest priority. Consider:
12	- Dependencies (what must be built before other things can work)
13	- Foundation vs polish (infrastructure before features)
14	- Blocking issues (what's preventing progress)
15	- Stage progression (complete earlier stages before later ones)
16
17	Do NOT just pick the first item in a list. Use your judgment about what will provide the most value or unblock the most work.
18
19	Announce your choice and briefly explain WHY you chose it before proceeding.
20
21	## Step 3: Implement the Feature
22
23	Work on ONLY this single feature. Do not scope creep. Do not "also fix" other things. Stay focused.
24
25	## Step 4: Test the Feature
26
27	- If tests exist for this feature area, run them and ensure they pass
28	- If no tests exist, write appropriate tests for the feature you just implemented
29	- All tests must pass before proceeding
30
31	## Step 5: Update the PRD
32
33	Find the `current_*` document that serves as the PRD/plan (likely `current_PRD.md` or similar). Update it to reflect:
34	- Mark the completed item as done (change `"passes": false` to ` "passes": true]` if using that or change "done" to true)
35	- Note any design decisions made during implementation
36	- Update any sections that are now outdated
37
38	## Step 6: Append to Progress File
39
40	Find `current_PROGRESS.md` (or the equivalent progress journal tracking file). Append a new entry to the Session Log with:
41	- Today's date
42	- What feature was implemented
43	- Key implementation details
44	- Any issues encountered and how they were resolved
45	- What tests were added/run
46
47	## Step 7: Git Commit
48
49	Stage and commit all changes with a clear commit message describing the feature implemented.
50
51	Do NOT push unless explicitly asked.
52
53	---
54
55	## CRITICAL RULES
56
57	1. ONE FEATURE ONLY - Do not work on multiple features. Stop after completing one feature cycle.
58	2. TESTS REQUIRED - Do not skip testing. Either run existing tests or write new ones.
59	3. DOCUMENT EVERYTHING - The progress file is your memory between sessions. Be thorough.
60	4. COMMIT ATOMICALLY - Each /ralphonce invocation should result in exactly one focused commit.

People who liked this also viewed

6 picks

Type