Skip to content
Back to search

senior-mode

MarketplaceWorks with Claude CodeGitHub

senior-mode and its companion plugins.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 18 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Sycatle/senior-mode with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Sycatle/senior-mode'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/sycatle--senior-mode/badge.svg)](/listings/sycatle--senior-mode)

HTML

<a href="/listings/sycatle--senior-mode"><img src="/api/listings/sycatle--senior-mode/badge.svg" alt="findsafeskills safety rating" /></a>

Install

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines
  1. {
  2. "name": "senior-mode",
  3. "owner": { "name": "sycatle" },
  4. "description": "senior-mode and its companion plugins.",
  5. "plugins": [
  6. {
  7. "name": "senior-mode",
  8. "source": "./plugins/senior-mode",
  9. "description": "Makes AI-assisted coding work like a senior engineering team: framing, specs and ADRs, TDD, atomic commits, a GitHub Projects roadmap, required reviews and bounded autonomous agents."
  10. }
  11. ]
  12. }
README.md · README · 138 lines
  1. # senior-mode
  2. **English** · [Français](README.fr.md)
  3. A Claude Code plugin that makes AI-assisted coding work like a senior engineering team. Ideas get
  4. framed before anyone codes. Decisions are written down. Tests come first and commits stay small.
  5. The roadmap lives on a GitHub Project. Every change is reviewed, and nothing merges without passing
  6. checks. The process scales with the task: a typo never gets an ADR.
  7. Status: v0.1, early. What works today and what is coming is marked below.
  8. ## Is it for me?
  9. - **You build with AI but things get messy.** senior-mode asks the questions you would forget,
  10. writes the plan down and keeps a clean history, so you end up with an app you can show, hand over
  11. or audit.
  12. - **You are a developer.** You get TDD, atomic Conventional Commits, specs and ADRs, a reviewer with
  13. a fresh context, and model routing per task (haiku to read, sonnet to build, opus to decide), with
  14. no extra ceremony for small tasks.
  15. - **You run a small team.** The board, the statuses and the protected zones make an AI teammate's
  16. work visible and bounded. A human approves what touches CI, security, data or architecture.
  17. It does not fit you if you want a one-shot code generator, or if your project does not live on
  18. GitHub.
  19. ## Start in 60 seconds
  20. In Claude Code:
  21. ```
  22. /plugin marketplace add Sycatle/senior-mode
  23. /plugin install senior-mode@senior-mode
  24. ```
  25. Then, in your project (an existing repository or an empty folder):
  26. ```
  27. /senior-mode:setup
  28. ```
  29. It shows what it will change on GitHub and waits for your yes. Then it creates the Project board,
  30. labels, merge rules, git hooks and the check list. Run it again at any time to repair. Then:
  31. ```
  32. /senior-mode:frame I want users to be able to export their invoices as PDF
  33. ```
  34. You need [`gh`](https://cli.github.com/) logged in (`gh auth refresh -s project` for the board),
  35. `git` and `jq`. More in [Getting started](docs/guide/getting-started.md).
  36. ## A typical day
  37. 1. **Frame.** `/senior-mode:frame` interviews you a few questions at a time, offers alternatives
  38. with a recommendation, then writes the spec, the ADRs and tickets with acceptance criteria,
  39. size, priority and milestone.
  40. 2. **Build.** For each ticket: a branch, failing tests first, the code, small conventional commits.
  41. The checks run before each push and publish `senior-mode/ci`.
  42. 3. **Review.** A `reviewer` agent with a fresh context reviews the PR against the spec and against
  43. engineering standards, then sets `senior-mode/review`.
  44. 4. **Merge and release.** Rebase merge once both statuses are green. Changes to protected zones wait
  45. for a human. release-please turns the commits into a changelog and a version.
  46. ```mermaid
  47. flowchart LR
  48. idea([Idea]) --> frame[frame: questions, spec, ADRs]
  49. frame --> issues[Tickets on the board]
  50. issues --> tdd[Branch, failing tests, code]
  51. tdd --> pr[Pull request]
  52. pr --> ci{{senior-mode/ci}}
  53. pr --> review{{senior-mode/review}}
  54. ci --> merge[Rebase merge]
  55. review --> merge
  56. merge --> release([Release])
  57. ```
  58. The walk-through, step by step: [A typical day](docs/guide/a-typical-day.md).
  59. ## Commands
  60. | Command | What it does | State |
  61. |---|---|---|
  62. | `/senior-mode:setup` | Adopt a repository: board, labels, merge rules, ruleset, checks, hooks, templates, release-please. Safe to rerun. | Available |
  63. | `/senior-mode:frame` | Turn an idea into decisions, a spec, ADRs and ready tickets. | Available |
  64. | `next` | The daily session: board state, then delivers the top ready ticket with you. | [Coming in v0.2](https://github.com/Sycatle/senior-mode/milestone/2) |
  65. | `status` | Plain-language dashboard: done, in progress, blocked, waiting for you. | [Coming in v0.2](https://github.com/Sycatle/senior-mode/milestone/2) |
  66. | `run` | Delivers up to N ready tickets on its own, within the guardrails. | [Coming in v0.3](https://github.com/Sycatle/senior-mode/milestone/3) |
  67. | `retro` | Weekly: reprioritise, list debt, turn repeated mistakes into checks. | [Coming in v0.4](https://github.com/Sycatle/senior-mode/milestone/4) |
  68. Behind them, nine small discipline skills load only when they apply (triage, ready, tdd, commit,
  69. verify, spec, adr, grill, review), and seven agents each have their own model and effort (scout,
  70. researcher, architect, test-author, implementer, reviewer, ops). Hooks deny force-pushes, pushes
  71. to the default branch and skipped checks, and keep code edits out of a framing interview. See
  72. [Commands](docs/guide/commands.md), [Skills](docs/guide/skills.md), [Agents](docs/guide/agents.md)
  73. and [Autonomy and guardrails](docs/guide/autonomy.md).
  74. ## No CI budget? No problem
  75. By default the checks run on your machine before each push and publish their result as a commit
  76. status (`ci.mode: local`). GitHub still refuses a merge without it. If you have an Actions budget,
  77. `ci.mode: actions` adds a workflow that runs the same list on GitHub and releases. See
  78. [Configuration](docs/guide/configuration.md).
  79. ## How it compares
  80. Two collections inspired senior-mode, and they are excellent. Pick the one that fits.
  81. | | senior-mode | [superpowers](https://github.com/obra/superpowers) | [mattpocock/skills](https://github.com/mattpocock/skills) |
  82. |---|---|---|---|
  83. | Focus | Delivery on GitHub, from idea to release | Development discipline inside a session | Alignment and spec-to-tickets, small composable skills |
  84. | Framing interview | Yes (`frame`, `grill`) | Yes (brainstorming) | Yes (`grill-me`, `grill-with-docs`) |
  85. | TDD, review | Yes, review sets a required status | Yes, two-stage review | Yes |
  86. | Issues and board | GitHub Issues and Projects (fields, milestones) | No | GitHub or GitLab issues, sub-issues, dependencies |
  87. | Merge rules and CI | Ruleset, required statuses, local or Actions CI | No | No |
  88. | Model per task | Pinned per agent | Per role, by guidance | No |
  89. | Autonomous multi-ticket run | Coming in v0.3 | One plan at a time | Yes (`implement-spec`) |
  90. | Platforms | Claude Code | Claude Code and many other agents | Claude Code and other agents |
  91. Choose **superpowers** if you want strong habits in every session across many coding agents and do
  92. not need GitHub process. Choose **Matt Pocock's skills** if you want small skills to adapt and
  93. already have your own workflow. Choose **senior-mode** if you want the whole path, from the first
  94. question to a reviewed, released change, enforced on GitHub. Facts checked in November 2026 against
  95. both repositories (superpowers v7.0.2, mattpocock/skills v1.3.2).
  96. ## Documentation
  97. - [User guide](docs/guide/README.md): install, a typical day, commands, skills, agents,
  98. guardrails, configuration, FAQ.
  99. - [Design spec](docs/specs/0001-senior-mode.md) and [decisions](docs/adr/).
  100. - [Changelog](plugins/senior-mode/CHANGELOG.md) and the [roadmap by milestone](https://github.com/Sycatle/senior-mode/milestones).
  101. ## Contributing
  102. Issues and pull requests are welcome. Read [CONTRIBUTING.md](CONTRIBUTING.md) first. Report
  103. vulnerabilities privately: see [SECURITY.md](SECURITY.md).
  104. ## License
  105. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.