Task Triage Skill
Canonical event ingress
Plane does not publish a task.inbox.new wire event. A Plane issue creation
travels through the signed n8n ingress and becomes
bloodbank.repo.task.created on
bloodbank.evt.repo.task.created. Use data.provider_event_type to confirm
plane.ticket.created, data.repo for canonical project identity, and
data.workspace plus data.board_id for provider provenance. Check the raw
ticket/state payload to decide whether the item is actually in the
inbox/backlog band; creation alone does not imply a particular lane.
Do not route by workspace alone. 33god and automaticai are tenant slugs on
the same self-hosted plane.delo.sh instance, and one workspace can contain many
boards. Board mapping comes from .project.json reconciled into the shared
Hermes registry. For the full transport and consumer journey, load
bloodbank-integration → references/event-journey.md.
There’s a large amount of friction when deciding:
- where a task should live
- how it fits into the overall system
- what dependencies are affected
- breaking the task into subtasks
- notifying the correct stakeholders
Handing this responsibility to a dedicated specialist promotes standardization, increases organizational potential, and decreases system entropy.
What problem does this solve?
- Lowers friction when going from idea to scoped plan.
- Improves organization by handing responsibility to a single agent
- Increases project velocity by reducing human cognitive load required to go from ‘idea’ to ‘scoped task’
Workflow
Think deeply about the task and answer the following questions:
- Why is this task likely being proposed?
- How would the end result lead to an improvement in the relative system(s) affected?
- Given the current state of the implied dependencies, does this task make sense in terms of overall improvement?
- Are there any recent issues, bugs, or complications that would likely have been mitigated or avoided had this been implemented or in place at the time of incident?
Determine the task’s classification
- Are this task’s dependencies bound by a single component (i.e. add a view to Holocene) or does this task require cross-component changes (i.e. Implement a new command - requires Holyfields schema, Bloodbank changes, new consumer service, etc), or does it refer to a single repo project or mobile app (i.e. Overworld, ChoreScore, Wean, SVGMe, etc)
- Is the task a metatask that doesn’t directly live in a component or domain, but contributes to improvements indirectly (i.e. research how BMAD workflows and skills can enhance each other, i.e. encapsulate the following workflow in a global skill)
- Is the task defining a new repo, component, or project that may require a plane project to be properly classified?
Determine the task’s (T0) approximate t-shirt size level of effort (LoE)
Decompose the task into a logical and reasonable set of subtasks described in a temp file T0-subtasks.md. Take care to include ticket classifications and stakeholders.
For each subtask in T0-subtasks.md repeat from step 3 with Tn where n=number of recursion levels with a hard max of nMAX=5
For each task/subtask generated, convert them to plane ticket dev stories in the appropriate project board’s backlog
When the request is to execute or orchestrate the resulting tickets — "work the board", "what's next", "clear the board", "orchestrate this ticket" — route to the momo skill. Momo is the 33GOD PM orchestrator: it surveys the board, triages, decides what to work next, and delegates all implementation to subagents. This skill (task-triage) scopes and creates tickets; Momo runs the board loop.
1---2name: task-triage3description: Facilitates a single point of ingress for any and all tasks. Used when pulling a new inbox/backlog task from a self-hosted Plane workspace, consuming the normalized `bloodbank.repo.task.created` fact (`data.provider_event_type=plane.ticket.created`), or handling any prompt that explicitly or implicitly describes a non-trivial task. Triggered by `add a feature`, `bloodbank.evt.repo.task.created`, or an equivalent provider-neutral task-created fact.4---56# Task Triage Skill78## Canonical event ingress910Plane does not publish a `task.inbox.new` wire event. A Plane issue creation11travels through the signed n8n ingress and becomes12`bloodbank.repo.task.created` on13`bloodbank.evt.repo.task.created`. Use `data.provider_event_type` to confirm14`plane.ticket.created`, `data.repo` for canonical project identity, and15`data.workspace` plus `data.board_id` for provider provenance. Check the raw16ticket/state payload to decide whether the item is actually in the17inbox/backlog band; creation alone does not imply a particular lane.1819Do not route by workspace alone. `33god` and `automaticai` are tenant slugs on20the same self-hosted `plane.delo.sh` instance, and one workspace can contain many21boards. Board mapping comes from `.project.json` reconciled into the shared22Hermes registry. For the full transport and consumer journey, load23`bloodbank-integration` → `references/event-journey.md`.2425There’s a large amount of friction when deciding:2627- where a task should live28- how it fits into the overall system29- what dependencies are affected30- breaking the task into subtasks31- notifying the correct stakeholders3233Handing this responsibility to a dedicated specialist promotes standardization, increases organizational potential, and decreases system entropy.3435## What problem does this solve?36371. Lowers friction when going from idea to scoped plan.382. Improves organization by handing responsibility to a single agent393. Increases project velocity by reducing human cognitive load required to go from ‘idea’ to ‘scoped task’4041## Workflow42431. Think deeply about the task and answer the following questions:44 1. Why is this task likely being proposed?45 2. How would the end result lead to an improvement in the relative system(s) affected?46 3. Given the current state of the implied dependencies, does this task make sense in terms of overall improvement?47 4. Are there any recent issues, bugs, or complications that would likely have been mitigated or avoided had this been implemented or in place at the time of incident?482. Determine the task’s classification49 1. Are this task’s dependencies bound by a single component (i.e. add a view to Holocene) or does this task require cross-component changes (i.e. Implement a new command - requires Holyfields schema, Bloodbank changes, new consumer service, etc), or does it refer to a single repo project or mobile app (i.e. Overworld, ChoreScore, Wean, SVGMe, etc)50 2. Is the task a metatask that doesn’t directly live in a component or domain, but contributes to improvements indirectly (i.e. research how BMAD workflows and skills can enhance each other, i.e. encapsulate the following workflow in a global skill)51 3. Is the task defining a new repo, component, or project that may require a plane project to be properly classified?523. Determine the task’s (`T0`) approximate t-shirt size level of effort (LoE)534. Decompose the task into a logical and reasonable set of subtasks described in a temp file `T0-subtasks.md`. Take care to include ticket classifications and stakeholders.545. For each subtask in `T0-subtasks.md` repeat from step 3 with `Tn` where `n=number of recursion levels` with a hard max of `nMAX=5`556. For each task/subtask generated, convert them to plane ticket dev stories in the appropriate project board’s backlog5657 When the request is to **execute or orchestrate** the resulting tickets — "work the board", "what's next", "clear the board", "orchestrate this ticket" — route to the **`momo`** skill. Momo is the 33GOD PM orchestrator: it surveys the board, triages, decides what to work next, and delegates all implementation to subagents. This skill (`task-triage`) scopes and creates tickets; Momo runs the board loop.
delorenj