sprint-pipeline

Automate phased feature implementation workflows in PANaCEa with audit-first planning.

Updated Nov 16, 2025
One-click install
npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill sprint-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-pipeline
Source: https://github.com/aaronjullger-lgtm/PANaCEa/tree/main/.claude/skills/sprint-pipeline
Command: npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill sprint-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end sprint implementation workflow for PANaCEa feature development. Use this skill whenever the user asks to "implement", "build", "add a feature", "plan and implement", "do it for me", or gives a multi-step technical task. This skill encodes Aaron's preferred phased audit-first approach and prevents half-finished implementations, forgotten test coverage, and uncommitted work.

Core Features & Use Cases

  • Audit-first planning: Inspect existing code, tests, and dependencies before coding.
  • Phased sprints: Break large features into numbered, testable sprints with clear goals.
  • Verification & commits: Ensure tests pass and commit messages are clear.
  • Progress continuity: Resume work across sessions without losing context.
  • Wiring discipline: Guidelines for UI wiring, config changes, and deployment steps.

Quick Start

Start by auditing the target feature, then plan and execute a phased sprint until all tests pass.

Frequently Asked Questions about sprint-pipeline

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

FAQPage Schema
How do I implement a feature in phased sprints with test-driven verification?

Automate end-to-end feature implementation by enforcing an audit-first, phased sprint approach that breaks tasks into numbered steps. This ensures test-driven verification and clear commit discipline before completing each sprint phase.

What is an audit-first approach for planning a feature implementation?

An audit-first approach inspects existing code, tests, and dependencies before coding begins. This structured sprint planning prevents half-finished implementations, forgotten test coverage, and uncommitted work.

How do I resume a multi-step technical task across different sessions?

Resume multi-step technical tasks across sessions using progress continuity features that maintain context. The workflow restores your previous sprint state, preventing lost work when implementing large features.

How do I prevent half-finished implementations and uncommitted work?

Prevent half-finished implementations by applying sprint guardrails that enforce test-driven verification and clear commit messages. The workflow ensures all tests pass before advancing to the next sprint phase.

Can I use this sprint workflow for planning and building UI wiring and config changes?

Yes, the sprint workflow supports multi-step technical tasks including UI wiring, config changes, and deployment steps. It provides specific wiring discipline guidelines to ensure structured implementation.

Do I need a specific framework to run phased sprint pipelines for feature development?

No external dependencies are required to run phased sprint pipelines for feature development. The workflow operates independently to automate end-to-end implementation tasks with test verification.