All authors
Claude Skills by TokiDEV
github.com/TokiDEV12 skills0 installs8 views
- Team Ceo ViewUse when a team-* skill (team-refactor, team-council, team-council-plan, team-kickoff, team-review) reaches a CEO gate and the human must approve, decline, or choose between options. Also when the user asks for a visual, HTML, or browser view of a decision, backlog, or plan, or wants to share a team-review gate with the owner of the branch it reviewed.Votes: 0GitHub stars: 3
- Team Council PlanUse when a council decision is recorded under `.council/decisions/` and the next step is planning how to carry it out, or when the user asks to plan the council's decision. Not for planning work the council never decided.Votes: 0GitHub stars: 3
- Team CouncilUse before the code exists, at a decision point that deserves more than one perspective: choosing between approaches, an architecture, an "are we sure?" before implementing. Also when the user asks for the council, a debate, or a PO, CTO or UX view on a choice. Not for reviewing code that exists: team-review (is it right?) or team-refactor (is it well-shaped?).Votes: 0GitHub stars: 3
- Team KickoffUse when starting a brand-new project or an empty directory, and the user wants several perspectives on its vision, scope, stack and conventions before the first line of code.Votes: 0GitHub stars: 3
- Team ProtocolUse when running any team-* skill (team-debate, team-plan, team-kickoff, team-refactor, team-review) — dispatching its role agents, settling what they disagree on, or handing off at a gate.Votes: 0GitHub stars: 3
- Team RefactorUse when code needs refactoring or cleanup, or its structure judged — god functions, tangled responsibilities, duplication, over-engineering, legacy code without tests, or code that resists the next change. Also when the user invokes Uncle Bob, Fowler, Beck, Feathers, Ousterhout, SOLID, KISS, YAGNI or clean code on existing code. Not for bugs, security or whether a change can merge: team-review.Votes: 0GitHub stars: 3
- Team ReviewUse when a change needs reviewing before it merges — a merge or pull request, a branch (yours or a colleague's), or an audit of a path or module for bugs, security holes, swallowed errors, missing tests, slow paths or a gap with what was asked. Also when the user asks for a code review, a security review, or whether a branch is ready to merge, and in the session that wrote a change, to leave its author's note for the review panel (a file under .council/, not the merge request's description or...Votes: 0GitHub stars: 3
- Team ScanUse before the first team-debate, team-plan, team-kickoff, team-refactor or team-review run in a project, when `.council/project-profile.md` is missing, or when the stack, conventions, installed skills or agents have changed since the profile was written.Votes: 0GitHub stars: 3
- Team AcceptanceUse when a pushed branch whose change shows in the app needs an acceptance page (recette, cahier de recette) to present it: each case with its steps, its expected result and screenshots taken on a running environment, in one page with a business view and a technical one. Also when the user asks for a recette, an acceptance page, or screenshots of what a branch does. Not for deciding or reviewing anything: team-review.Votes: 0GitHub stars: 3
- Team DebateUse before the code exists, at a decision point that deserves more than one perspective: choosing between approaches, an architecture, an "are we sure?" before implementing. Also when the user asks for the council, a debate, or a PO, CTO or UX view on a choice. Not for reviewing code that exists: team-review (is it right?) or team-refactor (is it well-shaped?).Votes: 0GitHub stars: 3
- Team PlanUse when a debate decision is recorded under `.council/decisions/` and the next step is planning how to carry it out, or when the user asks to plan the debate's decision. Also when executing a plan this skill wrote (its top names a `.council/decisions/` file). Not for planning work no debate decided.Votes: 0GitHub stars: 3
- Team ViewUse when a team-* skill (team-refactor, team-debate, team-plan, team-kickoff, team-review) reaches a gate and the human must approve, decline, or choose between options. Also when the user asks for a visual, HTML, or browser view of a decision, backlog, or plan, or wants to share a team-review gate with the owner of the branch it reviewed.Votes: 0GitHub stars: 3