dev-team

Plugin dev-team from marketplace maikelsoft-skills in Charmedme/maikelsoft-skills. Commands read from the repo's manifest — today.

Skills (7)

• deliver-story

  The team mode of dev-flow:build. Builds one large or risky work item with the dev-team agents, on the same chain as a solo build - the work folder in docs/work, the shared run.md header, spec.md with the fingerprints of the Behaviour spec, and one locked test file for each rule. The main session is

• medior-practice

  Rules and templates of the medior developer in the dev-team flow - plan a work package, build it test first, run the checks, report with real command output, and do one fix pass. Preloaded by the dev-team medior agents. Use when you act as a medior in a dev-team run.

• process-review

  The team mode of dev-flow:review-comments. Handles the comments of a pull request review on an item that the dev-team built (the run.md header says flow team). Reads the threads, sorts each comment into the classes of dev-flow, sends the fixes to the senior agent, has a second senior review the fix,

• senior-practice

  Rules and templates of the senior developer in the dev-team flow - design, the checks of spec.md, work packages, reflection on a design or core code, the locked acceptance tests, plan feedback, code review, the self-check, and the track record. Preloaded by the dev-team senior agent. Use when you ac

• stack-index

  Routing table from a file type, a package, or a technology to the dev-stack skill that holds its rules, with the state of each skill (available or planned). Preloaded by the dev-team agents. Use when a dev-team agent must know which stack skill to load before it designs, builds, or reviews code.

• story-intake

  Reads one work item (story, bug, task, or chore) from the work tracker (Jira, Azure DevOps, GitHub, GitLab, Linear) or from the human, read only, and writes spec.md of the work folder - the Behaviour spec copied with specsync.py and its fingerprints, and the item section with the acceptance criteria

• team-decisions

  The flow of team decisions in a dev-team run - the pre-filled decision sheet at G1, the decision index docs/dev-team/decisions.md, one ADR per decision, the user profile of earlier answers, the approval of a new package, a reopened decision, and decisioncheck.py. Use when a dev-team agent meets a de

Subagents (4)

• medior-large

  Medior developer of the dev-team flow for a package of size hard. Same job as the medior agent, with more reasoning effort. Plans one work package, builds it with tests, runs the checks, and does one fix pass after a review. Use when the senior agent gives a package of size hard to plan, build, or f

• medior

  Medior developer of the dev-team flow for a package of size standard. Plans one work package, builds it with tests, runs the checks, and does one fix pass after a review. Use when the senior agent gives a package of size standard to plan, build, or fix.

• security-reviewer

  Security reviewer of the dev-team flow. Reviews the full diff of one story one time, against the secure-coding rules, and tells the human what to do and what to check. Read only, except its own review file. Use when the deliver-story skill needs the one security review of a story.

• senior

  Senior developer of the dev-team flow. Designs a user story, reflects on a design or on core code, builds the critical core, and leads the mediors (one plan feedback and one code review per package). Use when the deliver-story skill needs a design, a reflection, the critical core, or the package lea

Hooks (2)

• SessionStart

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.py" || python "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.py" || py -3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.py"

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/log-command.py" || python "${CLAUDE_PLUGIN_ROOT}/hooks/log-command.py" || py -3 "${CLAUDE_PLUGIN_ROOT}/hooks/log-command.py"

Similar plugins