Skills System¶

Skills are Markdown files that define what Forge's AI agents produce and how they reason. They are the primary customization mechanism for adapting Forge to your team's stack.

How Skills Work¶

Each workflow stage — generating a PRD, analyzing a CI failure, implementing code — is driven by a skill. The skill defines:

• Output format and document structure
• Process steps and analysis frameworks
• Quality checklists and acceptance criteria
• Technology-specific conventions

Skills are loaded at runtime per ticket, resolved by Jira project key:

graph TD
    A[Ticket: AISOS-123] --> B{skills/aisos/ exists?}
    B -->|Yes| C[Load skills/aisos/analyze-ci/SKILL.md]
    B -->|No| D[Load skills/default/analyze-ci/SKILL.md]

This means a team only needs to provide the skills they've customized. Everything else falls through to the defaults automatically.

Directory Layout¶

skills/
├── default/              # Stack-agnostic defaults for all projects
│   ├── analyze-bug/
│   ├── analyze-ci/
│   ├── decompose-epics/
│   ├── fix-ci/
│   ├── generate-prd/
│   ├── generate-spec/
│   ├── generate-tasks/
│   ├── implement-review/
│   ├── implement-task/
│   ├── local-code-review/
│   └── review-code/
└── {project}/            # Per-project overrides (Jira key, lowercase)
    └── {skill-name}/
        └── SKILL.md

Available Skills¶

The Primary Way to Contribute¶

Writing a skill set for your team's stack is the fastest way to make Forge work better for your project — and to share that knowledge with others using similar tooling.

See the Authoring Guide for how to write a skill, and Default Skills for what the defaults already provide.