plan-milestone
Skill2 starsChanged 45 days agoMITView on GitHub
Use ONLY when the user explicitly types `$plan-milestone <milestone-or-feature-idea>`. Do not trigger implicitly from generic phrasing.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- adrian-wulf/vorarbeiter-gamedevtheir own version, first seen Oct 17, 2026
- Yesterday-AI/ytstacktheir own version, first seen Oct 13, 2026
- thaitype/sandcontainertheir own version, first seen Oct 13, 2026
- mattolson/agent-sandboxtheir own version, first seen Oct 8, 2026
- adrian-wulf/vorarbeiter-codetheir own version, first seen Sep 27, 2026
- jasoncrawford/claude-skillstheir own version, first seen Apr 25, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- mattolson/agent-sandbox★ 212same name
- adrian-wulf/vorarbeiter-code★ 2same name
- Yesterday-AI/ytstack★ 2same name
- jasoncrawford/claude-skills★ 1same name
- adrian-wulf/vorarbeiter-gamedev★ 0same name
- thaitype/sandcontainer★ 0same name
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 repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accept-milestoneSkill
- bootstrap-projectSkill
- bootstrap-stackSkill
- consult-expertSkill
- design-milestoneSkill
- finalize-workitemSkill
- implement-workitemSkill
- plan-workitemSkill
- repair-acceptanceSkill
- repair-discoverySkill
- repair-milestoneSkill
- repair-planSkill
- repair-workitemSkill
- run-milestoneSkill
- seal-milestoneSkill
- stabilize-milestoneSkill
- stack-guardSkill
- validate-discoverySkill
- validate-milestoneSkill
- validate-planSkill
- validate-workitemSkill
- accept-milestoneSkill
- amend-ssotSkill
- boilerplate-contextSkill
- bootstrap-designSkill
- bootstrap-projectSkill
- bootstrap-stackSkill
- consult-expertSkill
- design-milestoneSkill
- discover-productSkill
- finalize-workitemSkill
- implement-workitemSkill
- plan-milestoneSkill
- plan-workitemSkill
- repair-acceptanceSkill
- repair-discoverySkill
- repair-milestoneSkill
- repair-planSkill
- repair-workitemSkill
- research-packSkill
- review-docSkill
- run-milestoneSkill
- seal-milestoneSkill
- stabilize-milestoneSkill
- stack-guardSkill
- validate-discoverySkill
- validate-milestoneSkill
- validate-planSkill
- validate-workitemSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Treat all frontmatter keys other than name and description (e.g., agent:, disable-model-invocation:, allowed-tools:, context:, …
- Distinctive: line 16
If the source path no longer exists, this wrapper is stale — see ADR-010.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Source of truth: .claude/skills/plan-milestone/SKILL.md (skill 신설 근거: ADR-075 D4). Read it and follow the workflow.
Treat all frontmatter keys other than name and description (e.g., agent:, disable-model-invocation:, allowed-tools:, context:, argument-hint:, model:, effort:) as Claude-only and ignore them — execute locally in Codex.
Slash command translation: 본문 안의 /plan-milestone·/plan-workitem·/bootstrap-design·/discover-product 등 표기는 Claude 슬래시 커맨드다. Codex에서는 $plan-milestone 등으로 읽고 사용자에게 안내한다 (예: 본문 "다음 단계: /plan-workitem M2" → Codex 응답에서는 "다음 단계: $plan-workitem M2"). Codex CLI는 /를 빌트인 슬래시 커맨드에 쓰므로 명시적 치환이 필요.
Sub-agent parity: 본문 R2의 architect·R5-2의 designer 단발 sub-call은 Claude Agent 도구 기능이다. Codex 서브에이전트는 GA이나 본 저장소가 Claude persona 위임을 Codex subagent로 아직 매핑하지 않아 메인 세션이 순차 단일 실행으로 직접 추론한다(degrade — SKILL.md 본문의 Codex 노트 정합).
Preserve all repo policies from AGENTS.md and docs/.
If the source path no longer exists, this wrapper is stale — see ADR-010.
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.