forge
Skill4 starsChanged 6 months agoMITView on GitHub
Life coach planning skill. /forge day = daily review, /forge week = Sunday week plan, /forge month = last-Sunday month plan. Auto-detects mode from $ARGUMENTS and current date. Ends with Google Calendar push option. Trigger: "forge", "plan my day/week/month", "daily/weekly/monthly review".
78 other projects use a version of this.
Adopted by
Most recently taken up by
- venhdev/skillstheir own version, first seen Nov 8, 2026
- faizanio/FORGEtheir own version, first seen Nov 8, 2026
- jeanchristoph/claude_forgetheir own version, first seen Nov 6, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Nov 6, 2026
- rmkr/skillstheir own version, first seen Nov 5, 2026
- flopperj/dotfiles-coretheir own version, first seen Nov 4, 2026
Used with
Projects with it also use forge-ship, forge-review and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
redteamlifeSkillforge-ship
Use when the user asks to merge, release, promote, reconcile, or close out work in a repo containing `docs/forge/` or governed by FORGE. Not for per-task commits; those complete inside forge-execute-task.
Also in 6 projects that use this
tonmoy007Skillforge-review
Run a multi-dimensional parallel code review over the current change.
Also in 8 projects that use this
weselbenSkillforge-docs
Load before code changes, before writing docs or an ADR, when a user question exposes a missing how-to, and when closing a chunk of work; also loaded by forge after each squash-merge and by deep-research after a report.
Also in 3 projects that use this
DailenGSkillforge-design
Design, UX, and polish discipline for the forge lifecycle. Covers the design tier, the design brief in docs/DESIGN.md, UX requirements and their verification methods, the per-slice design pass, the UX defect register, and the release polish pass. Load whenever work touches a user-facing surface (GUI, terminal, library API, or operated service), whenever a UX observation needs disposing of, and whenever a release is in reach.
Also in 3 projects that use this
DshamirSkillforge-plan
Takes analysis.json + budget cap → derives the full phase sequence, hyperparameters, instance type, cost estimate, and acceptance thresholds. Emits plan.md (the single human gate document) and plan.json (the machine-readable spec that dispatch-v2 consumes). Refuses to plan if estimated cost exceeds budget×1.2.
Also in 4 projects that use this
- tonmoy007Skill
forge-build
Run Stage 6 of the Forge pipeline — implementation. Use when the user says
Also in 3 projects that use this
Other versions78 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 78
- cwinvestments/memstack★ 425same name
- ansari-project/codev★ 298same name
- cluesmith/codev★ 298same name
- swyxio/skills★ 194same name
- simota/agent-skills★ 96same name
- alp82/forge★ 36same name
- TT-Wang/forge★ 34same name
- emiliosheinz/agent-skills★ 20same name
- MetalLegBob/solana-vibes-kit★ 19same name
- kecoma1/MQL5-SKILLS★ 17same name
68 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cavemanSkill
- drawio-diagramSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- humanizerSkill
- karpathy-codingSkill
- software-docsSkill
- teachSkill
- write-a-skillSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 67 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Check $ARGUMENTS. If blank, check today's date:
- Distinctive: line 57
Ask: "Push week blocks to Google Calendar?
- Distinctive: line 74
Ask: "Push monthly checkpoints to Google Calendar?
- Distinctive: line 80
No new hard DSA on Saturday
“Common” is measured: kept by at least 6 in 10 of the 67 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Life coach for Vicky. MAANG Staff/Principal in 3 months. No fluff.
Step 0 — Detect Mode
Check $ARGUMENTS. If blank, check today's date:
- Last Sunday of month → MONTH
- Any Sunday → WEEK
- Otherwise → DAY
DAY FLOW
"Forge — Day Review. 5 questions."
- Win: "One win today?" — acknowledge in one line.
- Drain: "What drained energy and gave nothing back?" — if recurring across sessions, flag it.
- 3 Priorities: "Tomorrow: one MAANG goal, one job goal, one family/self goal." — cap at 3, push back if more.
- Deep Work Assignment:
- DSA → 05:20 block
- System Design / Behavioural / Article → 08:00 block
- Energy (1–5): ≤2 = review-only tomorrow. 3 = one new problem max. 4–5 = full day.
- Two consecutive ≤2 days → "50% load tomorrow. Sleep + family only."
Show plan then ask: "Push to Google Calendar? yes / skip"
Tomorrow — [DATE]
05:20 [MAANG task] 40 min
08:00 [Deep work task] 60 min
10:00 Staff job 7 hrs
18:45 Family protected
20:30 ForgeWEEK FLOW
"Forge — Week Plan. 6 questions."
- Retro: "DSA problems done? SD session done? Article written?" — flag gaps.
- DSA target: pattern + count. Suggest if blank: DP → Backtracking → weakest Stage 1–2.
- SD topic: one topic, two 08:00 sessions. Cycle: URL shortener → Rate limiter → Feed → Chat → Search → Ride share → Video.
- Article: lock topic now, write next Sunday.
- Life events: anything that shifts morning blocks?
- Energy forecast (1–5): ≤3 = light week, one new problem max. 4–5 = full week.
Ask: "Push week blocks to Google Calendar? yes / skip"
MONTH FLOW
"Forge — Month Plan. 5 questions."
- Campaign check: compare actual vs plan:
- Month 1 (Apr–May): DP + Backtracking + 5 SD templates + 5 leadership stories
- Month 2 (May–Jun): Advanced graphs + Greedy + 5 more SD + mock interviews
- Month 3 (Jun–Jul): Applications + 2 mocks/week + speed runs
- Adjust: what shifts next month based on actual pace?
- Applications (Month 3 only): companies, stages, blockers.
- Burnout audit: sleep, energy, family quality — any red? → one week at 50% load.
- Article pipeline: 4 topics for next month.
Ask: "Push monthly checkpoints to Google Calendar? yes / skip"
Guardrails
- Max 3 priorities per day
- No new hard DSA on Saturday
- Family blocks (07:00–08:00, 18:45–19:30) sacred — never fill
- Nothing past 20:45 — bed at 21:00
- Priority: System Design > DSA > everything else
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.