project-kickoff
Skill0 starsChanged 3 months agoMITView on GitHub
Use this when the opening DO KICKOFF section in AGENTS.md shows that a template has not been initialized.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- mahelmouzoun07-afk/project-kickofftheir own version, first seen Nov 8, 2026
- jonesrussell/skillstheir own version, first seen Nov 1, 2026
- adiutama/skillstheir own version, first seen Nov 1, 2026
- DPatta/project-docs-kittheir own version, first seen Nov 1, 2026
- Brandondaymdr/Claude-Skillstheir own version, first seen Oct 29, 2026
- romain-nicod/kickofftheir own version, first seen Oct 2, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- soumyaRauth/skills-hub★ 10same name
- adiutama/skills★ 1same name
- Brandondaymdr/Claude-Skills★ 1same name
- DPatta/project-docs-kit★ 1same name
- impeto-ai/claude-skills-impeto★ 1same name
- jonesrussell/skills★ 1same name
- lawalOyinlola/appsec-protocols★ 1same name
- Lucas-Grilli/context-os-plugin★ 1same name
- magi12345/project-kickoff★ 1same name
- openqa-labs/zenith★ 1same name
4 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- repo-layoutSkill
- skill-creatorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 5 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run this skill when AGENTS.md starts with a ## DO KICKOFF section.
- Distinctive: line 28
Ask one concise batch of only the questions still needed to establish durable context:
- Distinctive: line 47
Do not assume an answer when a choice materially affects the project.
- Very specific: line 49
Do not complete kickoff with the template's MIT license merely by omission: obtain an explicit decision about the LICENSE file first.
- Very specific: line 61
Only after the owner explicitly confirms the license, update LICENSE with the chosen license text, retain it when they explicitly choose …
- Very specific: line 70
Use the skill-creator skill to add a focused skill only when it has owned, reusable guidance:
- Very specific: line 73
Create tech-stack when framework, runtime, dependencies, or architecture need project-specific conventions beyond the shared context.
- Very specific: line 75
Create ui-ux when UI work is in scope and durable design or accessibility guidance exists.
- Very specific: line 77
Create testing when the project has established verification commands, test strategy, fixtures, coverage rules, or end-to-end workflow.
- Very specific: line 79
Create deployment when deployment is in scope and there is a repeatable environment, release, secrets, CI/CD, or rollback workflow.
- Distinctive: line 82
Do not create placeholder testing or deployment skills merely because those topics were discussed.
- Distinctive: line 88
After the confirmed context and justified skills are written:
- Distinctive: line 93
Do not leave template or kickoff language in the replacement README.
- Very specific: line 94
Remove the complete ## DO KICKOFF section from AGENTS.md, while keeping its completed project context and all other durable instructions.
- Very specific: line 96
Delete .agents/skills/project-kickoff/ as the final content change.
- Very specific: line 98
Run ./scripts/verify-harness.sh after deleting the skill, when the script exists.
“Common” is measured: kept by at least 6 in 10 of the 13 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
Project kickoff
Turn this template into a project-specific workspace through a short, evidence-based discovery process. The goal is to record confirmed durable context, not to design the project or fill the repository with empty skills.
When to run
Run this skill when AGENTS.md starts with a ## DO KICKOFF section. Finish
the kickoff before substantial implementation. Once that section is gone, this
skill is no longer needed and must not be recreated unless the user asks for a
new kickoff process.
1. Inspect before asking
Inspect the repository for existing code, manifests, documentation, CI, configuration, and design assets. Treat that evidence as authoritative. Do not ask questions that the repository already answers, and do not overwrite an existing codebase's conventions.
2. Ask focused questions
Ask one concise batch of only the questions still needed to establish durable context:
- Is this a new project or an existing-codebase migration?
- What problem, users, and primary outcome does the project have?
- What license should apply? For a new project, explicitly confirm whether to keep this template's MIT license, choose another license, or use no license. For an existing project, confirm the current license and ownership before changing it.
- For a new project: which language, runtime, framework, package manager, and major services should be used? For an existing project: confirm discoveries and ask only where choices are unclear.
- What commands should verify changes: tests, linting, formatting, type checks, builds, or end-to-end checks?
- Is deployment in scope? If so, what environment, platform, CI/CD workflow, secrets policy, release process, and rollback expectations apply?
- Is UI/UX in scope? If so, what design system, visual references, accessibility requirements, breakpoints, and interaction guidelines apply?
Do not assume an answer when a choice materially affects the project. If the
user defers a decision, record it as undecided rather than inventing a default.
Do not complete kickoff with the template's MIT license merely by omission:
obtain an explicit decision about the LICENSE file first.
3. Record the shared project context
Replace the placeholder in AGENTS.md with a concise project description,
confirmed architecture and conventions, and the canonical verification commands
when known. Keep broad, durable rules in AGENTS.md; do not put detailed
procedures there.
4. Apply the license decision
Only after the owner explicitly confirms the license, update LICENSE with the
chosen license text, retain it when they explicitly choose MIT, or remove it
only when they explicitly choose no license. Preserve an existing project's
license unless the owner directs a change. Include the resulting license in the
project README. Do not provide legal advice or choose a license on the owner's
behalf.
5. Create only justified skills
Use the skill-creator skill to add a focused skill only when it has owned,
reusable guidance:
- Create
tech-stackwhen framework, runtime, dependencies, or architecture need project-specific conventions beyond the shared context. - Create
ui-uxwhen UI work is in scope and durable design or accessibility guidance exists. - Create
testingwhen the project has established verification commands, test strategy, fixtures, coverage rules, or end-to-end workflow. - Create
deploymentwhen deployment is in scope and there is a repeatable environment, release, secrets, CI/CD, or rollback workflow.
Do not create placeholder testing or deployment skills merely because those topics were discussed. Each created skill must have a specific trigger, confirmed instructions, and verification steps.
6. Finish and clean up
After the confirmed context and justified skills are written:
- Replace
README.mdentirely with concise, project-specific documentation: purpose, setup, development and verification commands, deployment guidance when applicable, and any user-facing usage instructions that are known. Do not leave template or kickoff language in the replacement README. - Remove the complete
## DO KICKOFFsection fromAGENTS.md, while keeping its completed project context and all other durable instructions. - Delete
.agents/skills/project-kickoff/as the final content change. This skill is temporary scaffolding, not part of the initialized project. - Run
./scripts/verify-harness.shafter deleting the skill, when the script exists.
Summarize the decisions recorded, files created or removed, and important
unanswered questions. Verify that every remaining skill has valid frontmatter,
a description starting with Use this when, and fewer than 200 lines.
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.

