← ClaudeAtlas

sprint-architectlisted

Breaks a strategic Roadmap into a Work Breakdown Structure (components, dependencies, verification gates) and drafts the Implementation Plan before any code changes. Also runs the Legacy Onboarding Protocol for mature projects that predate this framework.
GstMirabal/Token-Optimized-Agent-Pipeline · ★ 0 · AI & Automation · score 72
Install: claude install-skill GstMirabal/Token-Optimized-Agent-Pipeline
# 🛠️ Local Skill: Sprint Architect (v2.0.0) ## Domain - **Category:** Project Management / Workflow Orchestration - **Origin:** Custom synthesis from `skills.sh` planning standards. - **Status:** `ACTIVE_LOCAL` - **Sovereignty:** `local` (Project-Specific) ## Technical Logic This skill provides the reasoning engine for the deconstruction of strategic Roadmaps. It implements the **"Planning-before-execution"** pattern, forcing the agent to perform a technical breakdown before proposing code changes. It also holds the core logic for the **Legacy Onboarding Protocol**. ## Procedures ### 1. WBS (Work Breakdown Structure) - The agent must segment each Roadmap Phase into: - **Components**: Physical areas of code affected. - **Dependencies**: Logical execution order (what must exist before what). - **Verification Gates**: Technical acceptance criteria for each task. ### 2. Implementation Plan Drafting - Mandatory plan structure: 1. **Goal**: Brief description of the change. 2. **Proposed Changes**: Grouped by component. 3. **Verification Plan**: Specific commands and tests. ### 3. Legacy Onboarding Protocol - When a mature project without this framework's roadmap hierarchy is detected, the agent MUST: 1. **Audit via Omni-Minimizer**: Invoke `skills/omni-context-minimizer/scripts/omni_minimizer.py` to extract the full AST structural skeleton of the legacy code. 2. **Retroactive Mapping**: Draft retrospective Roadmaps and Implementation Plans that reverse-engine