kickoff

Orchestrate product discovery, architecture planning, and environment provisioning for new software projects.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mckissinger/keel --skill kickoff-mckissinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kickoff
Source: https://github.com/mckissinger/keel/tree/main/skills/kickoff
Command: npx skills add https://github.com/mckissinger/keel --skill kickoff-mckissinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents chaotic greenfield development by guiding a project through the critical foundation decisions, architecture planning, design validation, and provisioning steps before feature implementation begins.

Core Features & Use Cases

  • Foundation Orchestration: Coordinates interviews, product specifications, architecture decisions, design-system gates, and environment provisioning in the correct order.
  • Project Readiness Workflow: Establishes a verified starting point with backlog definition, technical conventions, design direction, and development infrastructure.
  • Use Case: Start a brand-new application by defining its product goals, creating the foundation specs, preparing the design system, and reaching a green development environment ready for feature work.

Quick Start

Use the kickoff skill to guide me through setting up a new project foundation from initial decisions through provisioning and handoff.

Frequently Asked Questions about kickoff

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

FAQPage Schema
How do I structure a greenfield software project kickoff to avoid chaotic development?

A structured project kickoff orchestrates product discovery, architecture planning, design validation, and environment provisioning sequentially before feature development begins. This approach creates a durable foundation with verified specs, technical conventions, and a ready-to-build project baseline.

What is the correct workflow for establishing a new application foundation before coding?

Establishing a new application foundation requires sequential execution of interviews, product specifications, design validation, environment provisioning, and verification steps. This workflow defines product goals, backlog items, design direction, and infrastructure to reach a green development environment.

Can I skip architecture planning and design system validation for a new project launch?

Skipping architecture planning and design system validation risks chaotic greenfield development by bypassing critical foundation decisions. A structured kickoff workflow ensures design decisions, technical conventions, and environment setup are verified before feature implementation begins.

Does a project readiness workflow handle environment provisioning and backlog definition?

Yes, a project readiness workflow handles environment provisioning and backlog definition by orchestrating product discovery, architecture decisions, and design-system gates. It establishes a verified starting point with technical conventions, design direction, and development infrastructure ready for feature work.

What's the best way to define product goals and technical conventions for a greenfield project?

The best way to define product goals and technical conventions is through a structured kickoff workflow that coordinates product discovery interviews, architecture decisions, and design validation. This creates foundation specs and a verified project baseline before development starts.