Kickoff Project

    0

    Turn a vague project idea into a coding-agent-ready kickoff: requirements, architecture, a phased dev plan sized for small models, and an out-of-the-box project setup.

    Free

    1 useSecurity scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Kickoff Project

    Example session with this skill installed

    I want a CLI tool that auto-generates weekly reports from git commits

    • Read your context and instructions
    • Compiled the kickoff project

    Digging before producing. Phase 1 of 4 — each phase is confirmed before moving to the next.

    Q1 | Why do you want this? How are you writing weekly reports today?

    • A. All from memory — time-consuming, and I miss commits
    • B. I have a script/tool already, but the format is rough and needs manual upkeep
    • C. Other (please describe)

    My recommendation is A — the most common motivation, and it determines whether the tool should "draft" or "polish a template".

    ...

    Connects securely to your tools. The creator never sees your data.

    About this skill

    kickoff-project

    A project-kickoff skill that solves "I have an idea but don't know where to start, and handing it straight to an AI coder goes off the rails."

    It structures project kickoff into four phases, each confirmed with the user before moving to the next:

    1. Requirements

    Interviews from the user's perspective: what, for whom, core flow, boundaries. It digs before producing — when the user says "I want X", it first asks why and how they solve it today. Outputs a requirements doc that serves as the core context for all subsequent phases.

    2. Architecture

    Discusses tech choices and overall structure based on the requirements. Choices are driven by requirements, not tech preference, with trade-offs explained rather than conclusions alone; considers the user's existing experience and infrastructure; good-enough is enough, no over-engineering for hypothetical future scale.

    3. Phased Dev Plan

    Decomposes the architecture into sequential phases a coding agent can execute. The granularity anchor is a core design constraint: each phase must be independently completable by a 30B-param / 200K-context model — single concern, limited files, explicit inputs and outputs, independently verifiable completion criteria, explicit inter-phase dependencies. High-risk items get an upfront validation spike before scheduling; phase 1 is the MVP minimal validation path.

    4. Project File Init

    Writes all outputs into the target project so a coding agent works out of the box:

    • .agents/skills/ — requirements, architecture, and dev plan each as a standalone self-contained skill, loaded by the agent on demand
    • project-plan.md — dev plan + per-phase status (living doc, updated as development progresses)
    • AGENTS.md — project context overview and rules

    Design Traits

    • One question per turn (options + recommendation + allow custom) — no question dumps, no infinite questioning
    • Never asks what it can look up in the code/project
    • Not sycophantic: contradictory or infeasible answers are flagged and confirmed, never silently followed
    • Uncertain items are marked [TBD]; requirements the user never expressed are never fabricated
    • Key decisions require user confirmation — the skill never decides for the user

    The output is not documentation for humans but project infrastructure a coding agent can consume directly. Ideal for starting new projects, structuring vague ideas, or standardizing AI-assisted development workflows.

    Requires manual user confirmation at each phase transition. Does not generate application boilerplate code, only project structure and planning documentation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    1 use

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    Terminal / Shell
    Write Files
    Read Files
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    Unlike simple prompts that generate static text, this skill creates a persistent, agent-readable environment including a project-plan.md and dedicated skill directories designed for autonomous tools to navigate and execute.

    No, this skill focuses on "Architectural Design" and "Phase Decomposition" to create the blueprint; it prepares the environment so that specialized coding agents can then generate the actual code without hitting context limits.

    The skill uses a "one-question-per-turn" interview process to extract specific requirements and success metrics, ensuring the final architecture is based on your actual needs rather than generic assumptions.

    New in Agents & Orchestration