tjcages

@tjcages source repo

15 skills
0 followers
8 hours ago last updated

▌
Manifesto · tjcages bundle
Author and govern a product North Star (manifesto) that every feature is judged against — premise, non-negotiables, creed, decision checklist, conflict rule. Use when starting a non-trivial product/tool, when agents disagree about what the product is, when the user asks for a manifesto / north star / principles doc, before linear-setup on a project with no theory doc, or when running a drift audit against an existing manifesto. NOT for ticket CRUD or disposable weekend scripts.

0
installs
▌
Agent Worktrees · tjcages bundle
Isolate parallel AI agents on one git repo via branch+worktree, shared env symlinks, auto-ported previews, status lines, claims, and a land-from-main ritual. Use when ≥2 agents will touch this or any repo, the user asks to set up worktrees / parallel agents / agent isolation, or an agent is about to share a working tree with another. NOT for ordinary single-agent work on main.

0
installs
▌
Pr Writing · tjcages bundle
Write or review clear commit messages, PR titles, and PR descriptions that explain what changed and why. Use before writing git history or when asked to improve it. Not for code comments, chat replies, or docs pages.

0
installs
▌
Orchestrator · tjcages bundle
Owns complex multi-agent delivery as the sole root orchestrator. Use when the user says “orchestrate,” “act as the orchestrator,” “own the complete buildout,” “spin up subagents,” “manage agents until done,” or asks one root agent to own readiness, task progression, worker challenge, integration, and final delivery. Do not use for a spawned worker thread or a single bounded task that does not materially benefit from parallel work.

0
installs
▌
Progress Check · tjcages bundle
Give sparse, evidence-based progress updates for long-running agent tasks and projects. Use when work will take more than 15 minutes, spans multiple milestones, involves delegated agents, or when the user asks for progress bars, status cadence, fewer updates, or a global cross-agent progress rule. Not for short answers or tasks with no meaningful intermediate state.

0
installs
▌
Linear Sync · tjcages bundle
Sync, audit, or rescue an existing Linear project against repo reality. Use when the user asks to sync Linear, reconcile tracking, audit this project, fix a messy board, revive a parked project, or score readiness with the rubric. Runs discovery + confirmation before writes; never silent reorganize. NOT for first-time bootstrap (use linear-setup) or one-off CRUD.

0
installs
▌
Accept Gated AI · tjcages bundle
Make write-access AI trustworthy: every edit diffed, accept-gated, reversible, proportional, and willing to do nothing. Use when designing or auditing an agent that creates/updates/deletes user data, when adding overnight/batch AI passes, when a product’s AI writes feel silent or over-eager, or when the user asks for accept-gates / EditProposal / proposal substrate / undo-before-delete. NOT for read-only Q&A bots or coding-agent repository isolation.

0
installs
▌
Linear Setup · tjcages bundle
Bootstrap or extend Linear project tracking the right way — methodology, not API CRUD. Use when the user asks to set up Linear tracking, track this project in Linear, add this repo to Linear, backfill history, get ready to track, or consents after a soft-nudge from linear-discipline. Anchors to North Star, backfills Done with evidence, wires blockedBy, installs per-repo discipline. NOT for one-off issue create/comment — Linear MCP handles that.

0
installs
▌
Linear Monitor · tjcages bundle
Health-check Linear projects for slipping dates, stale In Progress, and orphan issues. Use when the user asks for a Linear health check, atRisk scan, monitoring, /linear-monitor, or when a Cursor Automation runs the Linear tracking health recipe. Default read + comment; no mass creates. NOT for bootstrap (linear-setup) or full rescue (linear-sync).

0
installs
▌
Linear Discipline · tjcages bundle
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.

0
installs
▌
Behavior Contracts · tjcages bundle
Keep multi-platform products behaviorally one product: write platform-neutral behavior contracts per form/primitive, let each kit satisfy them natively, audit contract drift (not screenshots). Use when adding a second surface (web/iOS/macOS), when parity tickets pile up, when lightboxes/composers fork, or the user asks for behavior contracts / platform parity / kit drift. NOT for single-platform apps or pure visual QA.

0
installs
▌
Constitution First · tjcages bundle
Author and govern a product North Star (constitution) that every feature is judged against — premise, non-negotiables, creed, decision checklist, conflict rule. Use when starting a non-trivial product/tool, when agents disagree about what the product is, when the user asks for a manifesto / constitution / north star / principles doc, before linear-setup on a project with no theory doc, or when running a drift audit against an existing constitution. NOT for ticket CRUD or disposable weekend scripts.

0
installs
▌
Linear Methodology · tjcages bundle
Proven methodology for building and tracking features, projects, and issues in Linear. Use when the user wants to set up Linear tracking, sync or audit a board, run a Linear health check, finish install after skills add, or keep session discipline honest. Routes to linear-setup / linear-sync / linear-monitor / linear-finish-install as needed; linear-discipline is always-on.

0
installs
▌
Lossless Migration · tjcages bundle
Inventory-before-rewrite: map every table/endpoint/engine/UI to a destination tag, prove zero regressions, retire only when replacement is live. Use when migrating/reframing an existing product, consolidating AI engines, or the user asks for an inventory audit / lossless migration / “don’t lose anything.” NOT for green-field apps with nothing to preserve.

0
installs
▌
Linear Finish Install · tjcages bundle
Finish Linear tracking pack install after skills are present: write always-on rules (Linear = default source of truth every session) and verify Linear MCP auth. Optionally offer Cursor Monitor Automation. Use when the user says "finish linear install", "finish linear-tracking install", "complete setup after skills add", or right after installing the pack.

0
installs

15 published skills