agentleFS
salmandevsalmandev/everything-gemini/skills/agency-sprint-runner/SKILL.md

agency-sprint-runner

Skill2 starsChanged 33 days agoApache-2.0View on GitHub

Executes an autonomous 4-stage software agency sprint (Spec -> Build -> Verify -> Certify) powered by Google Antigravity. Coordinates CEO, CPO, CTO, Fullstack Developer, Automation Tester, and CISO avatars from initial backlog to production release. Use when building end-to-end features, running full development cycles, or executing multi-role sprints.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Exit Gate: All 4 executives sign the Sprint Directive.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agency Sprint Runner (agency-sprint-runner)

The Agency Sprint Runner coordinates multi-role autonomous sprints across the virtual software agency. By moving work through four sequential, gated stages—Spec, Build, Verify, and Certify—it guarantees that features are built to specification, tested against regressions, vetted for security, and signed off before release.


🏃 The 4-Stage Sprint Execution Pipeline

flowchart LR
    subgraph S1["Stage 1: Specification"]
        CEO["CEO: Scope"] --> CPO["CPO: PRD & BDD"]
        CPO --> CTO["CTO: Architecture ADR"]
    end

    subgraph S2["Stage 2: Implementation"]
        CTO --> Dev["Fullstack Developer\nFrontend + Backend + DB Migration"]
    end

    subgraph S3["Stage 3: Verification"]
        Dev --> QA["Automation Tester\nPlaywright E2E + Unit Tests"]
    end

    subgraph S4["Stage 4: Certification"]
        QA --> CISO["CISO: Security Audit\nZero-Trust & Secret Check"]
        CISO --> Release["CEO: Gold Master Ship\nMerge & Release"]
    end

    S1 --> S2 --> S3 --> S4

📋 The 4 Gated Stages

Stage 1: Specification & Architecture Gate

  • Participants: ceo, cpo, cto, ciso.
  • Protocol:
    1. ceo sets the MVP scope boundaries.
    2. cpo drafts user stories with BDD acceptance criteria (docs/product/PRD.md).
    3. cto authors the Architecture Decision Record (docs/architecture/ADR.md) and selects the data model.
    4. ciso adds mandatory security invariants (authentication, RLS, input sanitization).
  • Exit Gate: All 4 executives sign the Sprint Directive.

Stage 2: Fullstack Engineering Gate

  • Participants: fullstack-developer.
  • Protocol:
    1. Implements database models and migrations with foreign key constraints.
    2. Implements backend API endpoints with input validation (Zod/Pydantic) and error envelopes.
    3. Implements responsive frontend UI components using modern component libraries (shadcn/ui, Tailwind).
    4. Runs type-checking (tsc --noEmit) and local unit tests with zero errors.
  • Exit Gate: PR diff passes linter and type-checker with clean, minimal changes.

Stage 3: Automated Quality & Regression Gate

  • Participants: automation-tester.
  • Protocol:
    1. Ingests BDD scenarios from the PRD and writes end-to-end Playwright tests.
    2. Executes tests covering Happy Path, error states, and responsive viewports (Mobile & Desktop).
    3. Asserts 100% passing tests with zero console exceptions or unhandled promise rejections.
  • Exit Gate: Formal QA Certification report (docs/qa/TEST_REPORT.md) passes.

Stage 4: Security Certification & Executive Sign-Off

  • Participants: ciso, ceo.
  • Protocol:
    1. ciso scans repository for hardcoded secrets, runs dependency audits, and verifies access control.
    2. ciso issues formal Security Clearance.
    3. ceo verifies business objectives and approves the final production release.
  • Exit Gate: Unanimous executive clearance; release tagged and ready to ship.

🚀 Running an Autonomous Sprint

Trigger an autonomous sprint in chat:

"Act as the agency-sprint-runner. Convene the agency avatars (ceo, cpo, cto, fullstack-developer, automation-tester, ciso) to execute an end-to-end sprint for: User Onboarding with Magic Link Authentication.

1. Stage 1 (Spec): CPO & CTO create PRD and ADR. 2. Stage 2 (Build): Fullstack Developer creates the database schema, auth API, and login page. 3. Stage 3 (Verify): Automation Tester runs E2E tests for successful login and expired token handling. 4. Stage 4 (Certify): CISO audits for credential hygiene, and CEO approves the release."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.