implementation-kickoff

Executes implementation tasks in an isolated Git worktree and produces one verified local commit.

3.7k|945|Updated May 31, 2025
One-click install
npx skills add https://github.com/openai/openai-agents-js --skill implementation-kickoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation-kickoff
Source: https://github.com/openai/openai-agents-js/tree/main/.agents/skills/implementation-kickoff
Command: npx skills add https://github.com/openai/openai-agents-js --skill implementation-kickoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It turns an agreed implementation scope into a clean, PR-ready local branch without touching the user's original checkout, while enforcing review, verification, and provenance rules before any commit is created.

Core Features & Use Cases

  • Isolated worktree execution: Fetches the latest origin/main, creates a detached worktree, and keeps all task changes uncommitted until final review passes.
  • Replay and verification gates: Replays the task diff onto the newest main, runs repository completion gates, and validates the final handoff with scripts/validate_handoff.py.
  • PR takeover support: Imports another author's pull request diff, preserves verified Co-authored-by provenance, and generates a complete PR draft without pushing or mutating GitHub.
  • Use Case: A maintainer asks the agent to implement a bug fix in openai-agents-js; the skill builds the change in a fresh worktree, runs final review, and hands off one clean local commit ready for the user to push.

Quick Start

Use $implementation-kickoff to start this implementation in a fresh worktree and leave one verified local commit.

Frequently Asked Questions about implementation-kickoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an implementation in an isolated Git worktree?

Explicitly invoke the skill after the implementation scope is agreed. It fetches origin/main, creates a detached worktree with git worktree add, keeps changes uncommitted, and finishes with one clean local commit on a suggested branch.

How do I take over someone else's pull request locally?

The skill refreshes the PR metadata and three-dot diff through read-only access, applies the complete task diff onto current origin/main, and records the original author as a verified Co-authored-by trailer. It never derives the branch from the contributor branch or preserves its commit topology.

Does this skill push branches or create pull requests on GitHub?

No. The skill never pushes, opens a pull request, or mutates GitHub in any way. It ends with a local branch and one commit, and explicitly reports that nothing was pushed.

What happens when origin/main advances during implementation?

The skill stashes task changes, rebases the detached HEAD onto the new origin/main, reapplies the stash, and reruns formatting and focused checks. If conflicts are ambiguous, it preserves the stash and stops for user direction.

Why does handoff validation fail on a seemingly clean worktree?

validate_handoff.py also detects hidden index states such as assume-unchanged flags, materialized skip-worktree paths, and dirty submodules that plain git status can miss. It also fails if committed paths do not exactly match the shipped-path manifest.