Coordinate end-to-end sprint execution from kickoff to closure.
npx skills add https://github.com/mikall/FactoryX --skill sprint-execution-mikall
Please help me install this Agent Skill. Skill: sprint-execution Source: https://github.com/mikall/FactoryX/tree/main/.claude/skills/sprint-execution Command: npx skills add https://github.com/mikall/FactoryX --skill sprint-execution-mikall
Sprint execution coordinates end-to-end engineering work including development, adversarial code review, iterative testing, security audits, and formal closure. This skill ensures alignment with master documents and gates before starting work.
Kick off sprint execution after requirements-analysis to coordinate development, reviews, testing, and closure.
High-intent search queries and answers about installing and using this skill.
Sprint execution coordinates the entire workflow by orchestrating kickoff, task allocation, development, adversarial code review, iterative testing, security audits, and formal closure. It enforces quality gates and exit criteria throughout the process to ensure alignment with project master documents.
Before starting sprint execution, you need master documents ready for implementation. The skill enforces prerequisites including a roadmap, testbook, and risk register, ensuring alignment with requirements-analysis outputs and functional or technical analyses.
Adversarial code review integrates into agile sprint workflows by enforcing rigorous review, bug detection, and quality gates during development. It acts as a checkpoint within the sprint execution process to ensure code quality before testing and security audits proceed.
Yes, you can run security and compliance checks during an active sprint. The skill integrates security and privacy audits alongside risk assessment directly into the sprint workflow, ensuring vulnerabilities are caught before formal closure and handover.
The best way to manage sprint closure is to enforce finish criteria, update changelogs, and generate handover artifacts. The skill coordinates formal closure by verifying that all testing, security audits, and quality gates have been satisfied.
You should not use automated sprint execution without a roadmap or risk register because the skill enforces these artifacts as prerequisites. Missing these master documents breaks alignment with requirements-analysis outputs and skips critical gates required for formal closure.
mikallExpand sprint roadmaps into atomic requirements with acceptance criteria.
gittowerOrchestrate a Git-based software release from version preparation to published verification.
jpeggdevExecute implementation plans by dispatching subagents with two-stage reviews.
owenlim225Consolidate project planning sections and specialized Claude Skills for lifecycle management.
