Create or update docs/WORKFLOW.md from a template to codify team workflow.
npx skills add https://github.com/rodacato/kwik-e-dev --skill workflow-rodacato
Please help me install this Agent Skill. Skill: workflow Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/launchpad/skills/workflow Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill workflow-rodacato
Create or update docs/WORKFLOW.md — the complete team workflow covering build cycle (Issue → Branch → PR → Merge), sprint model, test strategy, playbooks, and definition of done. Use when the team has no written process for how work flows. Use when PRs keep getting merged without tests or reviews. Use when recurring operations (deploys, migrations) are tribal knowledge. Use when the definition of done is "when the author says so".
Write or update docs/WORKFLOW.md using the template at skills/workflow/template.md to capture your project’s workflow.
High-intent search queries and answers about installing and using this skill.
To document a team workflow from issue to merge, you can generate a docs/WORKFLOW.md file using a structured template. This codifies your build cycle, sprint model, test strategy, and definition of done into a single written contract.
A definition of done for agile teams is a formalized checklist ensuring code meets quality standards before merging. This workflow documentation process replaces subjective criteria with structured steps, test strategies, and explicit governance rules.
To create playbooks for recurring operations like deployments and migrations, you codify these processes within a central workflow document. This captures tribal knowledge into formal, repeatable steps for onboarding and governance.
Pull requests get merged without tests or reviews when a team lacks a documented workflow contract. Establishing a formal workflow file with defined steps, test strategies, and a definition of done enforces mandatory reviews before merging.
Yes, this workflow documentation approach works for agent-based workflows by providing a written contract for how work moves from idea to merged code. It supports onboarding and governance specifically for teams using Claude Code.
The best way to formalize tribal knowledge into a team process is by codifying recurring operations into a central workflow document. This translates undocumented deployments and migrations into formal playbooks with structured steps.
telum-aiCreate a Speck project structure with a skeleton project.md file.
gke-labsCompare pull request code changes against repository documentation maps to report drift.
shishiVerify Definition of Done and acceptance criteria for sprint increments.
saolalabGenerate project status reports and risk registers with Markdown templates and agile metrics.
