kickoff

Clarify implementation requirements and confirm git workflow before starting work.

Updated Apr 13, 2026

Search Tags:#git #planning #implementation #clarification #pr workflow #kickoff #branch strategy

Ready to run

npx skills add https://github.com/narusenia/skills --skill kickoff-narusenia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kickoff
Source: https://github.com/narusenia/skills/tree/main/kickoff
Command: npx skills add https://github.com/narusenia/skills --skill kickoff-narusenia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents rushed implementation by forcing upfront clarification of requirements, assumptions, and delivery boundaries before any work begins.

Core Features & Use Cases

Ambiguity Check: Identifies unclear requirements, overlapping interpretations, and hidden scope gaps before execution starts.
Git Workflow Alignment: Confirms branch strategy, commit granularity, and PR timing when the repository is under git management.
Scope Control: Separates what will be done from what will not be done, reducing rework during implementation, refactoring, or investigation-to-build transitions.

Quick Start

Use the kickoff skill to clarify the task, confirm the scope, and agree on the branch, commit, and PR plan before starting work.

Frequently Asked Questions about kickoff

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

FAQPage Schema

Why clarify implementation requirements before coding, and what does scope alignment prevent?▼

Clarifying implementation requirements before coding prevents ambiguity and rushed execution by forcing upfront confirmation of scope, assumptions, and delivery boundaries, reducing rework during development and refactoring.

How do I align git branch strategy and PR workflow before starting development?▼

Align git branch strategy and PR workflow by explicitly confirming branch naming, commit granularity, and PR timing with stakeholders before execution begins, ensuring all repository changes follow a synchronized delivery plan.

What is the best way to transition from code investigation to implementation without losing context?▼

The best way to transition from investigation to implementation is separating what will be done from what will not, resolving hidden scope gaps and unresolved questions before writing any code to prevent boundary creep.

Does this scope clarification approach work for debugging and refactoring tasks?▼

Yes, scope clarification applies to debugging and refactoring tasks by identifying overlapping interpretations and hidden scope gaps before execution starts, ensuring the delivery boundaries remain strictly controlled across all code modifications.

What happens if I skip scope confirmation and start implementation with unresolved questions?▼

Skipping scope confirmation allows unresolved questions and ambiguous requirements to reach execution directly, causing uncontrolled scope creep, misaligned branch strategies, and significant rework during the implementation phase.