Skip to content

tjcages/skills / linear-methodology/skills/linear-discipline

linear-discipline

Verified

Always-on Linear session discipline and one-time soft nudge for untracked repos. Use whenever non-trivial work is happening in a repo that already has a Linear tracking protocol in CLAUDE.md, AGENTS.md, or .cursor/rules; or when opening/working in a repo with no protocol and no .linear-tracking-skip file (ask once to run linear-setup). Enforces search-before-create, lifecycle, and close-the-loop. NOT for full bootstrap, sync, or monitor runs.

Linear discipline (always-on)

Chat rules: RESPONSE.md. Auth before Linear calls: AUTH.md.

Detect tracking

Tracked if the repo has a “Linear tracking” (or equivalent) section in CLAUDE.md, AGENTS.md, or .cursor/rules/* that names team + project.

Skipped if .linear-tracking-skip exists at repo root.

If tracked

Follow the protocol written in-repo:

  1. Search before create.
  2. Non-trivial work → file/update an issue in the named project + milestone.
  3. Backlog → In Progress at start → Done only when shipped.
  4. Close the loop before session end (state and/or comment).
  5. Prefer Linear’s generated branch names.

Before any Linear tool call: Step 0 auth.

If untracked and not skipped (soft nudge — 1B)

Ask once, one line, no preamble:

This repo isn’t tracked in Linear. Set it up now? (~10–20 min)

  • Yes → hand off to linear-setup (do not bootstrap inline without that skill’s gates).
  • No → create .linear-tracking-skip at repo root; stay quiet next time.
  • Never auto-create Linear projects or issues from a nudge alone.
  • Never nudge from Automation / linear-monitor runs.

If skipped

Stay quiet about setup. Still use Linear MCP for explicit user requests.

Out of scope

Full bootstrap → linear-setup. Rescue/audit → linear-sync. Health digest → linear-monitor.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall