brain-dump-workflow

Category: Tools & Productivity | Uploader: salmanrrana | Downloads: 0 | Version: v1.0（Latest）

MANDATORY quality workflow for Brain Dump tickets. Defines the exact MCP tool call sequence every ticket must follow. Load this before starting any ticket work. --- # Brain Dump Universal Quality Workflow > **Canonical source**: `src/api/ralph.ts` -> `getRalphPrompt()`. > This skill provides a quick reference. The system prompt has the full workflow. > > **MCP tools are consolidated**: 9 tools with action-dispatched params. > Always pass `action` as the first parameter to specify the operation. ## MANDATORY 5-Step Sequence Every ticket MUST go through these steps using MCP tools. Never skip any. ### Step 1: Start Work Call the **workflow** tool with `action: "start-work"` and `ticketId: "<id>"` BEFORE writing any code. This creates a git branch, sets status to `in_progress`, and posts a "Starting work" comment. ### Step 2: Implement + Verify Write code, then run quality gates: - `pnpm type-check` -- must pass - `pnpm lint` -- must pass - `pnpm test` -- must pass

Changelog: Source: GitHub https://github.com/salmanrrana/brain-dump

Directory Structure

Current level: .claude/skills/brain-dump-workflow/

📁 reference/
- 📄 compliance-logging.md 3.1 KB
- 📄 git-linking.md 1.8 KB
- 📄 review-guide.md 2.7 KB
- 📄 troubleshooting.md 3.6 KB
📁 scripts/
- 📄 run-quality-checks.sh 377 B
📄 SKILL.md 3.9 KB

SKILL.md

---
name: brain-dump-workflow
description: >
  MANDATORY quality workflow for Brain Dump tickets. Defines the exact MCP tool
  call sequence every ticket must follow. Load this before starting any ticket work.
---

# Brain Dump Universal Quality Workflow

> **Canonical source**: `src/api/ralph.ts` -> `getRalphPrompt()`.
> This skill provides a quick reference. The system prompt has the full workflow.
>
> **MCP tools are consolidated**: 9 tools with action-dispatched params.
> Always pass `action` as the first parameter to specify the operation.

## MANDATORY 5-Step Sequence

Every ticket MUST go through these steps using MCP tools. Never skip any.

### Step 1: Start Work

Call the **workflow** tool with `action: "start-work"` and `ticketId: "<id>"` BEFORE writing any code.

This creates a git branch, sets status to `in_progress`, and posts a "Starting work" comment.

### Step 2: Implement + Verify

Write code, then run quality gates:

- `pnpm type-check` -- must pass
- `pnpm lint` -- must pass
- `pnpm test` -- must pass

Commit with format: `feat(<ticket-short-id>): <description>`

### Step 3: Complete Implementation

Call the **workflow** tool with `action: "complete-work"`, `ticketId: "<id>"`, and `summary: "<what you did>"`.

This moves ticket to `ai_review` and posts a work summary comment.

### Step 4: AI Review (via MCP tools -- NOT local review skills)

IMPORTANT: Do NOT use local `/review` skills, subagents, or code review tools.
Perform self-review by reading your own diffs, then record findings via MCP.

For each issue found, call the **review** tool:

```
action: "submit-finding"
ticketId: "<ticket-id>"
agent: "code-reviewer"       // or "silent-failure-hunter" or "code-simplifier"
severity: "major"            // critical | major | minor | suggestion
category: "error-handling"
description: "Clear description of the issue"
```

Fix critical/major issues, then call the **review** tool:

```
action: "mark-fixed"
findingId: "<finding-id>"
fixStatus: "fixed"
```

Verify by calling the **review** tool with `action: "check-complete"` and `ticketId: "<id>"` -- response must contain `canProceedToHumanReview: true`.

### Step 5: Generate Demo + STOP

Call the **review** tool:

```
action: "generate-demo"
ticketId: "<ticket-id>"
steps: [{ order: 1, description: "...", expectedOutcome: "...", type: "manual" }]
```

Include 3-7 manual test steps. Ticket moves to `human_review`.

**STOP HERE. Do NOT continue. Only humans can approve tickets.**

## DO NOT

- Skip any step above
- Set ticket status to "done" directly
- Continue working after generating demo
- Write code before calling workflow `start-work`
- Use local review skills or subagents instead of review `submit-finding`
- Describe demo steps in text instead of calling review `generate-demo`
- Create git branches manually instead of using workflow `start-work`

## Severity Guide (for Step 4)

| Severity     | When to Use                                     |
| ------------ | ----------------------------------------------- |
| `critical`   | Bug that breaks functionality or causes crashes |
| `major`      | Incorrect behavior or error handling issue      |
| `minor`      | Code quality issue, not a bug                   |
| `suggestion` | Nice-to-have improvement                        |

## Demo Step Types (for Step 5)

| Type        | When to Use                      |
| ----------- | -------------------------------- |
| `manual`    | User performs an action          |
| `visual`    | User visually confirms something |
| `automated` | System runs a command/test       |

## Reference Docs

For detailed guidance on specific phases, see:

- `reference/review-guide.md` -- Self-review checklist and review agent details
- `reference/troubleshooting.md` -- Common errors and recovery steps
- `reference/git-linking.md` -- Linking commits and PRs to tickets
- `reference/compliance-logging.md` -- Enterprise conversation logging

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

brain-dump-workflow

Directory Structure

SKILL.md

Report

Notice