Reusable AI coding workflows a team member can install globally or per-project, in any environment: Cursor, Claude Code, and others.

• Bugfix -- Systematic bug resolution: assess the report, reproduce, diagnose root cause, fix, test, review, document, and submit a PR. Supports iterative PR feedback and an unattended mode. Used in the Flight Control projects (flightctl, flightctl-ui). See bugfix/README.md.

• Docs Writer -- Systematic documentation creation: gather context, plan structure, draft content, validate, apply changes, create merge request. Used in the edge-manager downstream docs project. See docs-writer/README.md.

• Triage -- Bulk Jira bug triage with AI-driven categorization and interactive HTML reports. See triage/README.md.

• PRD -- Requirements-to-PRD workflow: ingest requirements from Jira, clarify ambiguities through iterative Q&A, draft a Product Requirements Document, revise based on feedback, publish as a GitHub PR, and respond to reviewer comments. See prd/README.md and the PRD Guide.

• Design -- Design-and-decompose workflow: ingest a PRD, draft a technical design document, decompose into Jira-ready epics and stories, revise based on feedback, publish as a GitHub PR, respond to reviewer comments, and sync epics/stories to Jira. See design/README.md.

• Implement -- Story-to-code workflow: take a Jira Story, plan the implementation, write contract-based tests and production code via TDD, validate against the project's CI expectations, and manage review via GitHub PRs. See implement/README.md.

• E2E -- Story-to-tests workflow for [QE] stories: discover the project's e2e testing infrastructure, map acceptance criteria to test scenarios, write e2e test code following the project's patterns and reference suite, validate against anti-patterns and scenario coverage, and manage review via GitHub PRs. See e2e/README.md.

• Code Review -- AI-driven code review for uncommitted changes: discover project conventions, review with an independent reviewer perspective, present findings with honest implementor assessments for human decision, iterate until approved. Supports unattended mode for fully automated review-fix-iterate cycles. See code-review/README.md.

• CVE Fix -- Automated CVE remediation: read vulnerability details from Jira, apply multi-strategy dependency fixes, validate, create pull requests, backport to release branches, and close Jira tickets. Language-agnostic. See cve-fix/README.md.

• AI-Ready -- Scans a codebase and creates or updates AGENTS.md with project-specific build commands, test patterns, and coding standards. See ai-ready/README.md.

• KCS -- KCS Solution article workflow: gather bug context from Jira, draft a KCS article in markdown, validate against the KCS Content Standard, and produce a handoff message for the support engineer. See kcs/README.md.

• Skill Reviewer -- Meta-workflow that audits AI skill directories against eight quality dimensions. See skill-reviewer/README.md.

Each workflow is a directory with a SKILL.md (the mandatory entry point), optional phase skills under skills/, and optional command wrappers under commands/ -- all plain markdown, no IDE-specific syntax. Some workflows also include a skills/controller.md for phase dispatch, but this is an optional pattern. The installer auto-discovers every directory that contains a SKILL.md.

~/.ai-workflows/  (symlink to your clone)
  bugfix/
    SKILL.md, skills/, commands/
  docs-writer/
    SKILL.md, skills/, commands/

git pull updates everything instantly through the symlink.

Clone the repo and run the install script:

git clone https://github.com/flightctl/ai-workflows.git
cd ai-workflows

User-level -- available in all your projects:

./install.sh cursor

Project-level -- shared with anyone who clones the repo:

./install.sh cursor --project /path/to/project

User-level:

./install.sh claude

Project-level:

./install.sh claude --project /path/to/project

./install.sh all                          # user-level
./install.sh all --project /path/to/proj  # project-level

Each workflow is intended for a specific project or use case:

• bugfix -- the Flight Control projects (flightctl, flightctl-ui)
• code-review -- any project; reviews uncommitted changes against discovered project conventions
• docs-writer -- the edge-manager downstream docs project
• prd -- teams drafting Product Requirements Documents from Jira features
• design -- teams creating technical design documents and Jira-ready epic/story breakdowns from PRDs
• implement -- teams implementing Jira stories produced by the design workflow
• e2e -- teams writing e2e tests for [QE] stories produced by the design workflow
• cve-fix -- teams patching CVEs and updating vulnerable dependencies from Jira vulnerability tickets
• ai-ready -- onboarding any project for AI agents by generating AGENTS.md
• kcs -- teams writing KCS Solution articles for known issues with workarounds
• triage -- teams that want bulk Jira triage, categorization, and HTML reports from this repo or a clone
• skill-reviewer -- reviewing or standardizing Cursor/agent skills and skill packs (structure, clarity, completeness)

Use --workflows to install only the workflows relevant to a given project:

./install.sh cursor --project ~/flightctl --workflows bugfix
./install.sh cursor --project ~/edge-manager --workflows docs-writer
./install.sh --list                       # show available workflows

Invoke a workflow command (works in both Cursor and Claude Code):

• /bugfix:assess, /bugfix:diagnose, /bugfix:fix, ...
• /code-review:start, /code-review:continue, /code-review:clean
• /docs-writer:gather, /docs-writer:plan, /docs-writer:draft, ...

cd ~/.ai-workflows && git pull

./uninstall.sh                                          # user-level everything
./uninstall.sh cursor                                   # user-level Cursor only
./uninstall.sh cursor --workflows bugfix                # remove specific workflow
./uninstall.sh cursor --project /path/to/proj           # project-level Cursor
./uninstall.sh all --project /path/to/proj              # project-level everything

See CONTRIBUTING.md for how to add or modify workflows.

See LICENSE.