Convert plan documentation into sprint markdown and sync issues with Linear.
npx skills add https://github.com/edupazogle/agentic_cockpit --skill sprint-edupazogle
Please help me install this Agent Skill. Skill: sprint Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/sprint Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill sprint-edupazogle
This Skill turns backlog plans into sprint deliverables while keeping your architecture and project tracking in sync with Linear, reducing drift between documentation and execution.
docs/sprints/ markdown from docs/plans/ using PRD and architecture conventions.docs/architecture.md sprint timeline and cross-reference any newly created sprint docs.Use the sprint skill to convert your updated plans into sprint deliverables and sync the resulting sprint issues to Linear by running /sprint.
High-intent search queries and answers about installing and using this skill.
Sprint planning automation converts plan markdown into structured sprint docs and syncs execution artifacts with Linear issue tracking. It audits PRD references, generates sprint markdown with mermaid diagrams and acceptance tests, then creates or updates Linear issues using project UUID, milestone, team, and state metadata.
Generating sprint markdown with mermaid diagrams requires auditing existing plan documentation and architecture conventions. The process extracts PRD references, produces structured sprint docs containing implementation diagrams, demo scripts, and measurable acceptance criteria, then cross-references newly created docs within the architecture timeline.
Syncing sprint execution artifacts with Linear requires deterministic phase-by-phase execution to create or update issues using project UUID, milestone, team, state, labels, and blocks. The workflow audits existing issues first, applies correct sprint metadata, and performs post-run cleanup of processed plans to maintain tracking alignment.
Updating the architecture timeline automatically happens during sprint document generation by cross-referencing newly created sprint docs within docs/architecture.md. This maintains cross-document alignment between your architecture references and sprint execution artifacts, reducing drift between documentation and actual project tracking.
Automating sprint planning requires existing plan documentation in docs/plans/, architecture conventions in docs/architecture.md, and Linear project metadata including project UUID, milestone, team, and state. The deterministic execution workflow audits these PRD and architecture references before generating sprint deliverables and syncing issues.
Sprint documentation drifts from Linear issue tracking when plan updates bypass cross-document alignment. The sprint workflow prevents this by auditing PRD and architecture references, generating synchronized sprint markdown, updating the architecture timeline, and enforcing deterministic metadata sync with Linear project UUID, milestone, team, and state.
codejunkie99Orchestrate SystemVerilog RTL development from planning through verification.
BellaBeDefine acceptance criteria and generate validation plans with measurable metrics.
crazymsnFormat scientific Markdown documents with Mermaid diagrams and frontmatter metadata.
Lifecycle-Innovations-LimitedManage Linear issues and sprint planning via MCP tools.