Skill

Develop Full-Cycle Software Projects

A full-cycle coding skill that auto-detects project state and runs an adaptive 8-phase pipeline from planning through shipping.

Works with githubclaudecodexcursorantigravity

91
Spark score
out of 100
Updated 20 days ago
Version 14.1.0
Models
claude

Add to Favorites

Why it matters

Automate the entire software development lifecycle, from initial concept to deployment, adapting to project maturity and user needs.

Outcomes

What it gets done

01

Auto-detect project state (greenfield, in-progress, mature) and adapt workflow.

02

Execute an 8-phase engineering pipeline: Discover, Plan, Build, Test, Bug Hunt, Polish, Document, Ship.

03

Write production-grade code, tests, and documentation while respecting existing project conventions.

04

Implement a 3-strike failure recovery system for robust development.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-squirrel | bash

Overview

Squirrel - Full-Cycle Software Development Skill

A full-cycle coding skill working across 9 AI coding agents that auto-detects project state and adapts its 8-phase discover-plan-build-test-ship pipeline accordingly. Use it for greenfield builds, in-progress improvements, targeted bug fixes, or mature-codebase hardening; it does not replace environment-specific validation or expert review.

What it does

Squirrel is a full-cycle AI coding skill working across 9 AI coding agents (Claude Code, Codex, Cursor, Antigravity, Gemini CLI, GitHub Copilot, Windsurf, OpenCode, Aider) that auto-detects project state and adapts its 8-phase pipeline accordingly rather than applying a one-size-fits-all workflow. Step 0 classifies the project directory into a mode: an empty directory triggers Greenfield mode running all 8 phases from scratch, source files with no tests/docs trigger In-Progress mode (audit first, then improve), source plus tests plus CI plus README trigger Mature mode (targeted improvements only), and an explicit "fix this bug/add feature" request triggers Targeted mode (scoped work only). The 8-phase pipeline runs Discover (understand the project via code audit or requirements gathering), Plan (a concrete task list with dependencies and done-criteria), Build (write or modify code, using parallel sub-agents where the platform supports it), Test (run existing tests, write new ones, targeting 70%+ coverage), Bug Hunt (static analysis plus manual review), Polish (lint, format, type-check, remove dead code), Document (update README and inline docs without overwriting existing content), and Ship (a final checklist confirming tests are green, no secrets are present, and CI is configured). Failure recovery follows a 3-strike rule: on strike 1, fix the specific error and re-run tests; on strike 2, re-read the code and try a different approach; on strike 3, stop, revert, document what failed, and ask the user rather than continuing to force a fix. Its best practices require respecting existing code conventions (matching naming, test framework, import style, architecture, reading 2-3 similar files before writing a new one), and it explicitly never suppresses type errors with as any/@ts-ignore, never deletes failing tests to make a suite pass, and never leaves code in a broken state.

When to use - and when NOT to

Use it when starting a new project from scratch, improving an existing codebase, fixing bugs, adding features or refactoring, adding tests/linting/CI to a project, writing production-grade documentation, or whenever the request is a multi-step "build me"/"fix this"/"squirrel this project" development task. Its limitations note it does not replace environment-specific validation or expert review, CI/CD templates it generates are starting points rather than drop-in guarantees, and parallel sub-agent execution depends on the host platform actually supporting it.

Inputs and outputs

Inputs: a project directory (any state - empty, in-progress, or mature) and a development request (build, fix, improve, add tests/docs/CI).
Outputs: depending on the detected mode and phase scope - new project code built through all 8 phases, or a scoped fix/improvement applied to an existing codebase, always ending in a shippable state with green tests, no secrets, and configured CI.

npx skills add flyingsquirrel0419/squirrel-skill

Who it's for

Developers who want an adaptive, full-cycle coding assistant that figures out where a project actually stands and jumps in at the right phase - from greenfield builds to targeted bug fixes to hardening a mature codebase - across whichever of the 9 supported AI coding agents they use.

Source README

Squirrel is a full-cycle AI coding skill that works across 9 AI coding agents. It auto-detects project state (greenfield, in-progress, or mature) and adapts its 8-phase engineering pipeline accordingly. Instead of a one-size-fits-all workflow, it figures out where the project actually is and jumps in at exactly the right point.

FAQ

Common questions

Discussion

Questions & comments ยท 0

Sign In Sign in to leave a comment.