Run any Skill in Manus with one click

$pwd:

linear-brasa

Name: Linear Brasa
Author: wilsonfreitas

// Manage the Linear workflow for the brasa project: saving ideas as issues, and refining/planning issues using EnterPlanMode and updating them in Linear. Use this skill whenever the user mentions Linear, saving an idea, refining a ticket, or planning a feature — even if they don't explicitly say "Linear" but the context is clearly about brasa development tasks.

Run Skill in Manus

$ git log --oneline --stat

stars:40

forks:7

updated:April 17, 2026 at 10:22

SKILL.md

readonly

name	linear-brasa
description	Manage the Linear workflow for the brasa project: saving ideas as issues, and refining/planning issues using EnterPlanMode and updating them in Linear. Use this skill whenever the user mentions Linear, saving an idea, refining a ticket, or planning a feature — even if they don't explicitly say "Linear" but the context is clearly about brasa development tasks.

Linear Brasa Workflow

You manage the entire development lifecycle for the brasa project in Linear.

Announce at start: "I'm using the linear-brasa skill to manage the brasa project in Linear."

Always use the Linear MCP tools (mcp__linear-server__*) for all communication with Linear — never use the gh CLI or direct API calls.

Workspace constants (use these IDs directly — no need to look them up):

Team: Wilsonfreitas — ID 6c3534b0-9f98-476c-a1d6-3f99119e9f88
Project: brasa — ID 700095cc-dd63-405b-b285-1895aabce09d
Labels: Idea · Bug · Improvement · Feature
New issues always go to project brasa with status Backlog and no priority. The user can update these later during refinement/planning.

Flow 1 — Save an Idea

Trigger: user wants to capture an idea, feature request, or bug they thought of.

If the user gave only a title, ask for a short description (one paragraph is enough — or proceed without one if they say it's enough as-is).
Ask which label fits: Idea, Feature, Improvement, or Bug.
- Default to Idea when the user is still exploring and hasn't refined it yet.
- Suggest the most likely label based on context, but let the user confirm.
Create the issue via mcp__linear-server__save_issue:
- team: Wilsonfreitas team ID
- project: brasa project ID
- status: Backlog
- priority: no priority (omit the field)
- labels: the chosen label
Confirm with the issue identifier (e.g., WIL-42 created).

Flow 2 — Refine (Design) an Issue

Trigger: user wants to brainstorm and produce a design for an existing issue — "refine WIL-X", "brainstorm WIL-X", "design WIL-X".

Delegate to the linear-brasa-brainstorm skill. That skill handles fetching the issue, running the brainstorming flow, saving the ## Design section, the user review gate, and the label conversion from Idea to Feature / Improvement / Bug.

Flow 3 — Plan an Issue

Trigger: user wants to write an implementation plan for an already-designed issue — "plan WIL-X", "write the plan for WIL-X".

Delegate to the linear-brasa-plan skill. That skill validates the presence of ## Design, runs the plan-writing flow, and saves the ## Implementation Plan section.

General Notes

Always write issue titles and descriptions in English, even if the user describes the idea in another language (e.g., Portuguese). Translate the user's input before creating or updating the issue.
Always confirm destructive or irreversible actions (e.g., marking Done) before executing.
When the user references an issue by number only (e.g., "WIL-42" or just "42"), look it up via mcp__linear-server__get_issue.
Keep issue descriptions clean markdown — no raw HTML, no escaped characters.
If the user asks something that doesn't clearly fit one of the three flows, ask a clarifying question rather than guessing.

related-skills.json

same repository

brasa-db-explorer.md

from "wilsonfreitas/brasa"

Connect to BrasaDB's DuckDB database and execute SQL queries to explore Brazilian financial market data. Use this skill whenever the user asks to query, explore, analyze, or study data in the brasa database, asks about available datasets or tables, wants to run SQL queries against financial data, wants to create views or combine datasets for a specific application, or mentions DuckDB, BrasaDB, or SQL in the context of this project. Also trigger when the user asks questions that could be answered by querying the data — e.g., "what stocks are in IBOV?", "show me PETR4 prices", "what's the DI1 curve?", "help me create a view with these datasets", "I have datasets A and B, combine them for X".

2026-04-1840

linear-brasa-executor.md

from "wilsonfreitas/brasa"

Execute a previously-planned Linear issue for the brasa project end-to-end: read the plan from the issue, work through each step/phase/task faithfully, maintain an "Execution log" comment on the issue, check off items in the plan's checklist as they complete, and only mark the issue Done after all tests, ruff, and pre-commit pass. Use this skill whenever the user says things like "execute WIL-X", "run the plan for issue X", "implement WIL-X", "carry out this issue", "let's do WIL-X", or otherwise wants to turn a planned Linear issue into actual code changes — even if they don't say the word "execute".

2026-04-1840

linear-brasa-brainstorm.md

from "wilsonfreitas/brasa"

Brainstorm and save a design spec into a Linear issue for the brasa project. Wraps superpowers:brainstorming but persists the final design as a `## Design` section inside the target issue's description instead of a `.md` file. Use whenever the user says "refine WIL-X", "brainstorm WIL-X", "design WIL-X", or otherwise wants to turn a brasa Linear issue into a reviewed design spec.

2026-04-1740

linear-brasa-plan.md

from "wilsonfreitas/brasa"

Produce an implementation plan from a brasa Linear issue's existing `## Design` section and save it as `## Implementation Plan` inside the same issue's description. Wraps superpowers:writing-plans but persists to Linear instead of a `.md` file. Use whenever the user says "plan WIL-X", "write the plan for WIL-X", or otherwise wants to turn an already-designed issue into an actionable plan.

2026-04-1740

brasa-template-writer.md

from "wilsonfreitas/brasa"

Write new brasa YAML templates from scratch or migrate legacy templates (with reader.function and handler-based fields) to the modern pipeline-based format. Use when the user asks to create a new template, write a template, migrate a legacy template, convert an old template, or work with YAML template definitions. Also trigger when the user mentions template creation, template migration, or refers to legacy/old templates.

2026-03-1140

package.json

"author": "wilsonfreitas"

"repository": "wilsonfreitas/brasa"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Project Management SpecialistsBusiness and Financial Operations Occupations13-1082L4

name	linear-brasa
description	Manage the Linear workflow for the brasa project: saving ideas as issues, and refining/planning issues using EnterPlanMode and updating them in Linear. Use this skill whenever the user mentions Linear, saving an idea, refining a ticket, or planning a feature — even if they don't explicitly say "Linear" but the context is clearly about brasa development tasks.

Linear Brasa Workflow

You manage the entire development lifecycle for the brasa project in Linear.

Announce at start: "I'm using the linear-brasa skill to manage the brasa project in Linear."

Always use the Linear MCP tools (mcp__linear-server__*) for all communication with Linear — never use the gh CLI or direct API calls.

Workspace constants (use these IDs directly — no need to look them up):

Team: Wilsonfreitas — ID 6c3534b0-9f98-476c-a1d6-3f99119e9f88
Project: brasa — ID 700095cc-dd63-405b-b285-1895aabce09d
Labels: Idea · Bug · Improvement · Feature
New issues always go to project brasa with status Backlog and no priority. The user can update these later during refinement/planning.

Flow 1 — Save an Idea

Trigger: user wants to capture an idea, feature request, or bug they thought of.

If the user gave only a title, ask for a short description (one paragraph is enough — or proceed without one if they say it's enough as-is).
Ask which label fits: Idea, Feature, Improvement, or Bug.
- Default to Idea when the user is still exploring and hasn't refined it yet.
- Suggest the most likely label based on context, but let the user confirm.
Create the issue via mcp__linear-server__save_issue:
- team: Wilsonfreitas team ID
- project: brasa project ID
- status: Backlog
- priority: no priority (omit the field)
- labels: the chosen label
Confirm with the issue identifier (e.g., WIL-42 created).

Flow 2 — Refine (Design) an Issue

Trigger: user wants to brainstorm and produce a design for an existing issue — "refine WIL-X", "brainstorm WIL-X", "design WIL-X".

Flow 3 — Plan an Issue

Trigger: user wants to write an implementation plan for an already-designed issue — "plan WIL-X", "write the plan for WIL-X".

Delegate to the linear-brasa-plan skill. That skill validates the presence of ## Design, runs the plan-writing flow, and saves the ## Implementation Plan section.

General Notes

Always write issue titles and descriptions in English, even if the user describes the idea in another language (e.g., Portuguese). Translate the user's input before creating or updating the issue.
Always confirm destructive or irreversible actions (e.g., marking Done) before executing.
When the user references an issue by number only (e.g., "WIL-42" or just "42"), look it up via mcp__linear-server__get_issue.
Keep issue descriptions clean markdown — no raw HTML, no escaped characters.
If the user asks something that doesn't clearly fit one of the three flows, ask a clarifying question rather than guessing.

linear-brasa

Linear Brasa Workflow

Flow 1 — Save an Idea

Flow 2 — Refine (Design) an Issue

Flow 3 — Plan an Issue

General Notes

More from this repository

More from this repository

Linear Brasa Workflow

Flow 1 — Save an Idea

Flow 2 — Refine (Design) an Issue

Flow 3 — Plan an Issue

General Notes