agentleFS
walutani1walutani1/gtm-groundwork/.claude/skills/kickoff/SKILL.md

kickoff

Skill0 starsChanged 3 months agoMITView on GitHub

Start this tool project properly - run the kickoff questions and the start-to-ship checklist. Use when the project is fresh (prd.md still a placeholder), or when the user says "kickoff", "let's start", or invokes /kickoff.

  • Reads credentials

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use standup, status 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.
  • AnthropicSkill

    standup

    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

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

The file

Files
SKILL.md

Kickoff

Run standards/new-tool-checklist.md from the top:

  1. Step 0 — the kickoff conversation (AskUserQuestion, recommendations attached): what are we building; AI layer (Vercel AI SDK vs Anthropic SDK); bulk model if needed; browser tooling (Playwright default vs Browserbase); org email provider (Google -> OAuth, else magic links); Supabase MCP token available; company-data policy check; .env.local present (if not, STOP and ask - it is always created manually, secrets never committed).
  2. Step 1 — PRD: hand off to /refine-prd (brain dump -> interview rounds -> Codex adversarial pass -> lock).
  3. Continue the checklist in order: mockup approval before code, scaffold verification, per-feature build loop with checkpoints, pre-deploy checks, deploy.

Record every kickoff decision in prd.md ("Kickoff decisions" section). When step 0 completes, set Stage: kickoff-done in prd.md and offer /refine-prd. Speak plainly (AGENTS.md, "Working with the user").

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.