Index of every page on this site: llms.txt
All skills
acedergren avatar

/phase-kickoff

@641a79b
Run it yourself

Use when starting a new development phase or sprint that needs branch creation, TDD test shell, and roadmap entry done together. Enforces phase scaffolding before implementation begins. Keywords: new phase, sprint start, feature branch, roadmap, test shell, scaffold. Triggers on "start phase" or "scaffold sprint".

Use this Skill: https://skilld.dev/gh/acedergren/agentic-tools/phase-kickoff

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈83 tokens for metadata: the name and description. ≈827 when used: this file.

Description uses 4.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈331 characters, or 4.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Phase Kickoff

When to Use

Load this skill when the user request matches the frontmatter description for Phase Kickoff.

Scaffold a new development phase: branch, test shell, and roadmap entry as one atomic operation. Enforces the invariant that implementation never starts without a branch and verification shell.

Do NOT load when

  • phase already exists and now needs execution rather than setup
  • task is a one-off fix with no roadmap or branch scaffolding
  • user only wants planning, not repository changes

NEVER

  • Never begin implementation before the branch and test shell exist — retroactively creating scaffolding after code is written means the test shell describes code that already exists rather than driving its design. The TDD shell's value is forcing you to name behavior before writing it.
  • Never create a phase entry without a concrete goal and verification criteria — vague roadmap entries ("improve auth") become unmergeable because nobody can agree what "done" means. The verification field must be a runnable command or an unambiguous observable outcome.
  • Never mix unrelated cleanup into the kickoff commit — the kickoff commit is the reference point for the phase. Mixed concerns make git bisect and phase diffing unreliable.
  • Never use a generic branch name like feature/phase3 — include the title slug so git branch -a is readable without cross-referencing the roadmap.

Expert decision points

When to split vs. extend a phase

If you're unsure whether work belongs in a new phase or extends the current one, ask:

  • Does it have a different primary deliverable?
  • Does it have different deployment risk?
  • Can it be reviewed independently?

Two YES answers → new phase. Otherwise extend.

Test shell structure determines phase quality

The describe hierarchy in the test shell is the phase's specification. Write it before the roadmap tasks, not after. If you can't write a meaningful it.todo("should...") for a task, the task is not well-defined enough to start.

Roadmap verification field

The verification field is a quality gate. Acceptable forms:

  • npx vitest run src/auth — runnable test command
  • curl -s localhost:3000/health | jq '.status == "ok"' — observable outcome
  • pnpm build && npx tsc --noEmit — build gate

NOT acceptable: "auth works", "tests pass", "looks good".

Script

bash scripts/scaffold-phase.sh "3 - User Authentication"

Outputs: branch name, test file path, roadmap stub.

Steps

  1. Parse $ARGUMENTS: Extract phase number and title (e.g., "3 - User Authentication")
  2. Append roadmap entry:
    ## Phase {N}: {Title}
    **Goal**: {one-sentence goal}
    - [ ] {N}.1 {task}
    **Verify**: {runnable command or unambiguous outcome}
  3. Create branch: git checkout -b feature/phase{N}-{kebab-case-title}
  4. Create TDD test shell with describe blocks matching roadmap tasks:
    describe("Phase {N}: {Title}", () => {
      describe("{N}.1 - {task}", () => {
        it.todo("should ...");
      });
    });
  5. Print summary: phase number, branch, test file path, task count

Arguments

  • $ARGUMENTS: Phase number and title — "3 - User Authentication" or "4 Real-time Notifications"

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7mo5 checks · Risk SAFE
  • Gen Agent Trust Hub8mo

    The skill is safe to use and provides helpful project scaffolding features. It automates development tasks such as creating git branches and test files. A minor risk exists for indirect prompt injection if a user provides a malicious phase title that the AI then uses to generate file content, but this is a common and low-severity concern for automation tools.

  • Socket8mo

    No alerts

  • Snyk8mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/2 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 641a79b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago

README badge

README badge for acedergren/agentic-tools/phase-kickoff