[ PORTABLE SKILL ]

linear-planning

This skill should be used when the user wants to plan a project, feature, or bug fix using Linear as the agent control plane. Use when the user says "plan this in Linear", "create Linear tickets", "break this down into tasks", "push to Linear", "set up our board for this feature", or wants to turn a description or spec into well-structured, agent-ready Linear issues. Requires the official Linear MCP server to be configured.

PART OF

bopen-tools →

Complete plugin installation is recommended so this skill keeps its agents, hooks, commands, and runtime context.

Claude pluginCodex pluginPortable skills

PUBLISHER: b-open-io
RELATIONSHIP: authored
VERSION: 1.0.3
BENCHMARK: unknown

[ RECOMMENDED INSTALL ]

Install bopen-tools

The complete plugin is the supported path. It preserves everything the publisher designed to work alongside this skill.

Claude Code

VERIFIED

Codex

VERIFIED

[ ADVANCED · INDIVIDUAL SKILL ]

Install only this skill

Use this narrower path only when you intentionally want the portable SKILL.md without the plugin’s surrounding capabilities.

Skills CLI

VERIFIED

Installs only the portable skill; it omits plugin hooks, agents, commands, apps/MCP configuration, and unlisted companion skills.

[ PROVENANCE ]

Trace it to the source.

DISTRIBUTED SOURCE: skills/linear-planning/SKILL.md ↗
UPSTREAM SOURCE: No separate upstream declared
DISTRIBUTED DIGEST: sha256:8223cef22366ce3230be8c5854bebd97f318d1b56303bb8d83a30dcadff6f584
LOCK HASH: Not applicable

Companion skills

No required companion skills are declared.

Agents using this skill

Tina

Executive assistant for Google Workspace — manages inbox, calendar, Drive, Docs, Sheets, Tasks, and Chat. Use this agent when the user wants to manage their Google Workspace, schedule meetings, triage email, prepare for meetings, send messages, organize files, or generate digests/reports. Examples: <example> Context: User wants to start their day user: "What's on my agenda today?" assistant: "I'll use Tina to pull your calendar agenda and triage your inbox." <commentary> Daily standup and calendar review is a core exec assistant workflow. </commentary> </example> <example> Context: User has an upcoming meeting user: "Prep me for my 2pm with the product team" assistant: "I'll use Tina to pull attendee info, relevant Drive docs, and recent email threads." <commentary> Meeting prep is a primary executive assistant use case. </commentary> </example> <example> Context: User wants inbox managed user: "Triage my inbox and flag anything urgent" assistant: "I'll use Tina to triage your Gmail and surface priority items." <commentary> Inbox triage for exec is a key workflow. </commentary> </example> <example> Context: User wants a weekly summary user: "Give me a weekly digest" assistant: "I'll use Tina to run the weekly digest workflow." <commentary> Weekly planning digest is a built-in GWS workflow skill. </commentary> </example>

Wags

This agent should be used when the user wants to plan, organize, or manage a project using Linear. Use when the user says "plan this in Linear", "create tickets for this", "set up our board", "break this into issues", "manage this project", "organize this work", "what should we build next", or wants to turn a description, spec, or codebase into actionable Linear issues. Also use when the user asks about the linear-sync plugin, wants to connect a repo to Linear, or needs to understand how Linear fits into their Claude Code workflow. Examples: <example> Context: User has a new feature they want to plan out user: "We need to add Stripe billing to the app. Can you plan this in Linear?" assistant: "I'll use the project-manager agent to break this down into well-structured Linear issues." <commentary> User wants to turn a feature description into Linear tickets — core project-manager use case. </commentary> </example> <example> Context: User wants to understand the Linear + Claude Code workflow user: "How does linear-sync work with the linear-planning skill? What's the difference?" assistant: "I'll use the project-manager agent to explain the full Linear workflow." <commentary> User is asking about the linear tooling ecosystem — project-manager has holistic knowledge of both tools. </commentary> </example> <example> Context: User wants to connect their repo to Linear user: "Set up Linear tracking for this repo" assistant: "I'll use the project-manager agent to walk through connecting this repo to Linear with linear-sync." <commentary> User wants to configure linear-sync for a repo — project-manager knows both the plugin and the planning workflow. </commentary> </example>

Related skills

ALL BOPEN-TOOLS SKILLS →

bopen-tools

advisor

Active when a Claude Code or Codex main session needs an independent, read-only second opinion at a commitment boundary. Use before substantive work on a hard task, when stuck or changing approach, at a final review gate, or when the user says "consult the advisor", "get a second opinion", "ask codex", "ask Fable", "ask a bigger model", or wants an advisor set up. Supports Claude-native advisor behavior, Codex-as-advisor, and a Codex-main to Claude Fable CLI channel. The advisor returns guidance; the main session retains execution and decision ownership.

authored0.0.2

bopen-tools

agent-auditor

Comprehensive audit skill for agents and skills across the plugin ecosystem. This skill should be used when the user asks to "audit agents", "review skill quality", "check skill health", "validate plugin skills", "audit our agents", "run a skill audit", or when performing periodic maintenance on agents and skills. Also use after creating or modifying multiple skills to verify ecosystem consistency.

authored0.1.2

bopen-tools

agent-decommissioning

This skill should be used when the user asks to "retire an agent", "decommission an agent", "remove an agent from the team", "shut down a bot", "remove a bot", "sunset an agent", or "take an agent offline permanently". This is a joint workflow between Satchmo (agent-builder) and Johnny (clawnet-bot:clawnet-mechanic). Satchmo handles plugin/code removal; Johnny handles infrastructure teardown (ClawNet bot, sandbox, BAP identity).

authored1.0.0

bopen-tools

agent-onboarding

Complete end-to-end checklist for adding a new agent to the bOpen team. Use when creating a new agent, onboarding a new team member, or need to remember the full agent deployment pipeline — design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.

authored1.1.1

bopen-tools

benchmark-skills

Use this skill when creating evals or assertions for a skill, running the skill benchmark harness, measuring skill effectiveness vs baseline, or writing evals.json files alongside skills. Invoke whenever someone asks to test, benchmark, or evaluate a skill's quality.

authored2.0.1

bopen-tools

charting

Full-stack data visualization and charting intelligence. This skill should be used when the user asks to "create a chart", "visualize this data", "build a dashboard", "plot this", "graph these metrics", "show me a chart of", "make a bar chart", "create a line graph", "build a heatmap", or needs help choosing the right chart type, selecting a charting library, or engineering the data pipeline from raw database state to rendered visualization. Covers chart selection, data transformation, library choice by scale, performance optimization, and accessibility.

authored1.0.0