kickoff
Skill1 starsChanged 30 days agoMITView on GitHub
Run the EzProject feature kickoff interview, then update INITIAL, ROADMAP, README, DECISIONS, AGENTS, and CLAUDE when present. Use when the user starts a new feature, project direction, or major initiative and wants the shared project documents populated before planning.
31 other projects use a version of this.
Adopted by
Most recently taken up by
- lukashouthoofd/cenekathontheir own version, first seen Nov 8, 2026
- takleb3rry/claude-global-appbuilding-skillstheir own version, first seen Nov 8, 2026
- ai-analyst-lab/interview-prep-with-aitheir own version, first seen Nov 8, 2026
- sassarini-marco/track-to-demotheir own version, first seen Nov 1, 2026
- sanjeevkumarraob/chartertheir own version, first seen Oct 25, 2026
- ncjsvr/skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use standup, grill and 2 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.
AnthropicSkillstandup
Generate a standup update from recent activity. Use when preparing for daily standup, summarizing yesterday's commits and PRs and ticket moves, formatting work into yesterday/today/blockers, or structuring a few rough notes into a shareable update.
Also in 3 projects that use this
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 5 projects that use this
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
Other versions31 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 31
- Maximepodgorski/agent-skills★ 21same name
- syutolee/digital-marketing-skills-pack★ 10same name
- ai-analyst-lab/interview-prep-with-ai★ 9same name
- 0x43e96f/skills★ 8same name
- zauberzeug/game-of-cards★ 7same name
- takleb3rry/claude-global-appbuilding-skills★ 6same name
- ArangoGutierrez/claude-toolkit★ 4same name
- adrian-wulf/vorarbeiter-code★ 2same name
- bluewhalelabs/claude-skills★ 2same name
- Kohulan/orthonym-skills★ 2same name
21 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audit-projectSkill
- cleanupSkill
- create-skillSkill
- dailySkill
- dependency-checkSkill
- documentSkill
- execute-prpSkill
- ez-project-workflowSkill
- fix-issueSkill
- generate-prpSkill
- housekeepingSkill
- monitor-setupSkill
- nextSkill
- performanceSkill
- pipelineSkill
- refactorSkill
- retrospectiveSkill
- review-codeSkill
- rollbackSkill
- security-scanSkill
- statusSkill
- tddSkill
- upgrade-statusSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run a short interview, one question at a time, then update the project docs from the answers.
- Very specific: line 11
Read .ezproject.json if it exists to detect mode and stack.
- Very specific: line 12
If stack is auto (with stack_pending: true), set STACK_PENDING = true, skip the stack question, and run the Stack Advisor step (5) after …
- Distinctive: line 25
Update all relevant files:
- Distinctive: line 35
Wait for user confirmation, then run:
- Distinctive: line 44
Ask one question at a time.
- Distinctive: line 45
Keep the conversation in French unless the user asks otherwise.
- Distinctive: line 46
Keep generated file content in English for portability.
- Distinctive: line 47
Remove placeholders instead of leaving them behind.
- Distinctive: line 48
Keep the MVP concrete and small.
- Very specific: line 49
If STACK_PENDING and the user pushes back on the recommendation, listen — they know their context better than the heuristics.
“Common” is measured: kept by at least 6 in 10 of the 24 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
Kickoff
Run a short interview, one question at a time, then update the project docs from the answers.
Workflow
- Read
.ezproject.jsonif it exists to detect mode and stack.- If
stackisauto(withstack_pending: true), setSTACK_PENDING = true, skip the stack question, and run the Stack Advisor step (5) after the interview.
- If
- Interview the user one question at a time:
- what they want to build
- why it matters and who uses it
- core stack and data sources (skip stack question if
STACK_PENDING) - outputs, constraints, MVP scope, environment
- Read:
AGENTS.mdCLAUDE.mdif presentROADMAP.mdREADME.mdDECISIONS.mdexamples/ortemplate/examples/
- Update all relevant files:
INITIAL.mdROADMAP.mdREADME.mdAGENTS.mdCLAUDE.mdif presentDECISIONS.mdif new architecture decisions were made (always add an ADR for the stack choice when STACK_PENDING was true)
- Stack Advisor (only if STACK_PENDING): score the answers (Q1/Q4/Q5/Q7) against the 4 stacks and recommend one with concrete justification.
- Stacks:
data(parsing, ETL, scrape→DB/sheet),api(REST endpoints),ai-agent(LLM agents, MCP),web(server-rendered UI). - Watch for hybrids (e.g., statements→sheet with auto-categorize =
data+ai-agentpatterns). Pick a primary, optionally a secondary for cherry-picked patterns. - Wait for user confirmation, then run:
EZ_ROOT=$(python -c "import json; print(json.load(open('.ezproject.json'))['ezproject_root'])") powershell -ExecutionPolicy Bypass -File "$EZ_ROOT/ez-finalize-stack.ps1" -ProjectPath "$(pwd)" -Stack <chosen> - For hybrids, also
cp "$EZ_ROOT/template/examples/<secondary>/<file>.py" examples/(1-2 files max).
- Stacks:
- Present the generated scope and ask for confirmation before moving on to PRP generation.
Rules
- Ask one question at a time.
- Keep the conversation in French unless the user asks otherwise.
- Keep generated file content in English for portability.
- Remove placeholders instead of leaving them behind.
- Keep the MVP concrete and small.
- If STACK_PENDING and the user pushes back on the recommendation, listen — they know their context better than the heuristics.
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.