Project Setup: plan, backlog and verifier before code

    3

    Before your agent writes product code: a classified plan, a risk-ordered backlog with checkable Done-when criteria, agent instructions, and a verifier that fails loudly.

    Free

    2 installs5.0 (1 review)

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Project Setup: plan, backlog and verifier before code

    Example session with this skill installed

    Set up this repo for the story flow using the project-setup skill. It is an existing Python library. Story ID prefix: CAN.

    • Read your context and instructions
    • Compiled the project setup

    Summary

    The repo scan is done and nothing has been written yet. Existing-project mode needs your approval before any file changes, so here are the findings and the plan.

    Real run from our install test on a small Python library, lightly trimmed.

    Proposed classification

    Modeexisting
    Product typeSDK/library (Python, requires-python >=3.9)
    Lifecycleprototype
    Surfacespublic Python API only: no UI, CLI, CI or release pipeline
    Story ID prefixCAN (CAN-001, CAN-002)
    Deliverydual-agent: Claude implements, Codex reviews, one fix pass, you open the PR and merge

    Gap analysis

    AreaClassEvidenceProposed action
    Source and testsAdopttextstats/ plus a 2-case unittest suitenone
    VerifierAdaptthe scaffold drafted pytest -q, which isn't installedscripts/verify-project.sh runs python3 -m unittest discover -s tests -v
    Profile, plan, backlogAddnone existcreate them with the CAN prefix
    Agent instructionsAddno CLAUDE.md or AGENTS.mdCLAUDE.md plus an AGENTS.md symlink
    Design specAvoidno UIleave it out

    Riskiest assumption

    The library has no technical risk; the unknown is whether the story flow runs end to end here. So

    CAN-001 is a small real change pushed through the whole flow, with Done-when: bash scripts/verify-project.sh exits 0 on its branch.

    After approval: setup committed to main. Setup validation passed and bash scripts/verify-project.sh passes on the existing tests. Files: CLAUDE.md, AGENTS.md, four docs (profile, plan, backlog, engineering guide), specs/_TEMPLATE.md, notes/_TEMPLATE.md, scripts/verify-project.sh. Nothing was overwritten.

    Next steps

    • Start the first story: start story CAN-001
    • Review the generated verifier commands before relying on them

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

    About this skill

    What it does

    The problem. Agents start coding before anyone decided what the product is, what "done" means, or which assumption could sink it. The result is a backlog of vague tasks and a verifier nobody wrote.

    What the skill does. It classifies the product (web, SaaS, mobile, API, CLI, SDK, data, AI and more), finds the riskiest assumption and puts it first in the backlog, and writes every Done-when item as a command or an artifact check. It generates the plan, backlog, engineering guide, AGENTS.md and CLAUDE.md, and scaffolds scripts/verify-project.sh from your stack markers.

    Why not just prompt for it. The skill ships templates, a bootstrap script with a dry run, a validator, and a verifier scaffold that writes a failing TODO when it cannot recognize your stack, so an unconfigured project never reports a fake pass.

    Use it when you start a greenfield product or adopt an existing repository for agent-assisted delivery.

    Known limits.

    • Software projects only.
    • Generated verifier commands are a starting point; review them before relying on them.

    Where it fits

    1. Project Setup (this skill), once per repository: plan, backlog, verifier
    2. Story Flow or Codex Dual-Session Story Flow, once per story: build, verify, independent review
    3. You: read the diff, push, open the PR, merge
    4. Merged Worktree Cleanup, after the merge: remove the worktree and branch

    Project Setup is optional but recommended: without it the story flows fall back to auto-detected checks, with no backlog or project-owned verifier.

    How to use

    1. Unzip into your Claude Code or Codex skills folder.
    2. Say set up this project or set up this repo for the story flow.
    3. Review the dry-run file list and approve it.

    Requirements

    python3 and bash. Works in Claude Code and Codex CLI.

    Works best with: Story Flow (runs each backlog story) and Merged Worktree Cleanup.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    2 people have installed this skill.

    Trust & safety

    Security scanned

    Verified clean 4 days ago

    • Free to download with an account

    Requires

    Python 3
    Bash

    Listed4 days ago

    What's inside

    Frequently Asked Questions