Agent skill

Team Boot

by tikalk in tikalk/adlc-team-skills

A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…

MITAuto-check passedDevelopment

Install Team Boot

skills CLI
$ npx skills add tikalk/adlc-team-skills --skill team-boot -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tikalk/adlc-team-skills team-boot --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tikalk/adlc-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team/team-boot .claude/skills/team-boot && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
team-boot
GitHub stars
141
Token cost
~2.2k tokens
SKILL.md length
1,037 words
Files
5 (incl. scripts, references)
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…

  • Works in 3 steps: Read .adlc/init-options.json from the… → If unconfigured (missing, null, or path… → If configured: assemble the context and…
  • A session starts
  • SKILL.md covers Overview, Class Boots, Event hook (automatic) and Manual fallback (agents…, plus 4 more sections
  • Runs PowerShell and Shell scripts from its folder

What it does

Team Boot is an agent skill from tikalk/adlc-team-skills. Use when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index, Class Boots catalog, skills registry — is not yet injected; also fires the session-end friction trigger for CDR/ADR/PDR capture with pending-decision safety nets.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/decision-capture.md`, `references/manual-fallback.md` and `scripts/boot.sh`).

It sits in Development, covering Architecture decision records. The repository describes itself as: Agent skills for the Agentic SDLC: team lifecycle (team-boot, team-learn, team-init, team-repair), software factory, evals, CDR lifecycle with confidence scoring, and… The licence is MIT.

When your agent uses it

  • A session starts
  • Resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution
  • Class Boots catalog
  • Skills registry — is not yet injected

Example prompts

  • “/team-boot”

Requirements

  • A Bash shell
  • PowerShell

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read .adlc/init-options.json from the current working directory.
  2. If unconfigured (missing, null, or path doesn't exist): invoke the
  3. If configured: assemble the context and follow the Class Boots catalog

What it can do on your machine

Read from SKILL.md and the folder at commit 2dbed36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (PowerShell and Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Team Boot loads about 2.2k tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 1,037 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from tikalk/adlc-team-skills at commit 2dbed36, republished under its MIT licence (© tikalk). 1,037 words, ~2,226 tokens.

Download SKILL.mdSave it as .claude/skills/team-boot/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
team-boot
description
Use when a session starts or resumes after compaction (auto via the session_start and session_compact event hooks) and the team AI directives context — constitution, CDR index, Class Boots catalog, skills registry — is not yet injected; also fires the session-end friction trigger for CDR/ADR/PDR capture with pending-decision safety nets.
scripts.sh
scripts/boot.sh
scripts.ps
scripts/boot.ps1

team-boot

Overview

Assembles team AI directives context and injects it into the system prompt at session start. The CDR index lists all available team context modules with descriptors — read full module files on demand when a task matches.

team-boot injects only the always-relevant layer: constitution titles, the compact CDR index, the Class Boots catalog, the skills registry, and MCP servers. The four record classes (ADR/PDR/ChDR/CDR deep-dive) plus technology selection load on demand through the class boots below — each pairs its index injection with decision capture.

Discovery is native: the injected CDR index is matched by the LLM against the current task on its own, per prompt, with no skill invocation. /team-discover is a separate, user-invoked command for explicit structured re-discovery (e.g., starting a complex feature) and is not part of the bootstrap loop.

Fast path: if the team AI directives context (constitution, CDR index, Class Boots catalog) is already in your system prompt or first user message, the event hook already ran — do nothing.

Class Boots

BootInjectsInvoke WhenCapture Via
architect-bootADR index (docs/adlc/memory/adr/ + legacy .adlc/memory/adr/)architecture work; tech-stack/pattern choicedirect write to .adlc/drafts/adr/
product-bootPDR index (docs/adlc/memory/pdr/ + legacy .adlc/memory/pdr/)product/feature scope, personas, monetizationdirect write to .adlc/drafts/pdr/
change-bootChDR index (docs/adlc/memory/chdr.md + legacy .adlc/memory/chdr.md)change-history rationale, reverts, issue-linked commitsdirect write to .adlc/drafts/chdr/
team-levelupCDR module bodies (team-ai-directives)session end; CDR descriptor match; reusable team patterndirect write to adlc branch drafts/cdr/
tech-radar-bootTikal Tech Radar contextchoosing/evaluating technologyradar context + direct write to .adlc/drafts/adr/

Invoke a class boot when a task or decision matches its row — invoke it at the START of the matching task, before planning the todo list and before implementation, so the class context informs planning. Never defer to session end. When no local memory index exists in the current working directory and the directory sits inside a workspace (detected via a .gitmodules marker in an ancestor), the boot reads the workspace root's docs/adlc/memory/ index instead. Each boot emits its class context section and its own searched line (_Searched N <class> records, K matched._), and carries the full detection and capture guidance for its class. 0 rows matched → the boot emits its section heading + the searched line only — no table.

Event hook (automatic)

The session_start and session_compact event hooks (declared in .events.json, wired by adlc-cli) run scripts/boot.sh (POSIX) or scripts/boot.ps1 (Windows), which reads .adlc/init-options.json, assembles the context block (constitution, CDR.md index table, .skills.json), and outputs it to stdout. The plugin caches the result and pushes it into the system prompt on every step (idempotent — same cached content, no accumulation). The session_compact declaration makes post-compaction re-injection part of the contract: when a harness summarizes history, the generated plugin re-runs the handler and the dedup guard prevents double-injection. Agents whose adapters don't map session_compact yet skip it — adlc-cli owns those mappings.

Manual fallback (agents without event support)

  1. Read .adlc/init-options.json from the current working directory. Do NOT walk up parent directories. Do NOT use glob, find, or any file-search tool to locate it.
  2. If unconfigured (missing, null, or path doesn't exist): invoke the team-setup skill.
  3. If configured: assemble the context and follow the Class Boots catalog above. Full walkthrough in references/manual-fallback.md.

Decision Capture

Detect decisions as they emerge and write lightweight drafts directly to .adlc/drafts/{type}/ during the session — no specify skill invocation needed. The only gate is clarify at session end.

Detection Triggers
PatternTypeDrafts toClarify via
Tech stack choice, pattern selection, "we chose X over Y"decisiondrafts/adr//architect-clarify
Feature scope, persona, monetizationproductdrafts/pdr//product-clarify
Reusable team rule, "we always do X"patterndrafts/cdr//team-levelup
Revert/hotfix rationale, issue-linked commit, git command w/ human-authored message, authored PR title/body, CHANGELOG editincidentdrafts/chdr//change-clarify
Workaround adopted, "X for now because Y"workarounddrafts/chdr//change-clarify
Operational constraint, "only works because Z"constraintdrafts/adr//architect-clarify
Change abandoned, "simplifying X but Y blocks it"abandoneddrafts/chdr//change-clarify
Eval criterion discoveredevaldrafts/evals//evals-clarify

Proportionality gate and trust model in references/decision-capture.md: match documentation depth to how non-obvious the decision is, and synthesize project knowledge — never transcribe instructions.

Show full SKILL.md (366 more words)Show less
Team Context & Decisions (every response)

Every response carries ONE merged section — grounding context rows and owed decision rows in the same 6-column table:

markdown
## Team Context & Decisions

| ID | Name | Type | Rel | Status | Clarify |
|--|--|--|--|--|--|
| CDR-YYYY-NNN | <name> | <type> | <relevance> | in use | — |
| — | <decision> | <ADR/PDR/CDR/ChDR/Eval> | <trigger> | pending | <clarify skill> |

_Scope: N CDRs · A ADRs · P PDRs · C ChDRs · E evals · M skills — J rows shown · Unrecorded: N pending · Unclarified: M captured drafts._

Status in use + Clarify — = grounding context (accepted records only). Status pending/captured/clarified/handed off + Clarify skill = owed decisions. No draft row may carry Status in use — drafts appear only as pending decision rows. J = all rows shown.

  • Detect: match session decisions against triggers above.
  • Classify: assign record type (ADR/PDR/CDR/ChDR).
  • Write: write a lightweight draft directly to .adlc/drafts/{type}/ using the family draft template.
  • Track: update the table row (ID = draft ID or —, Status = pending/captured/clarified/handed off, Clarify = matching skill).
  • Surface: mirror each detected decision as a task-list todo (draft → matching clarify skill at session end). After code-modifying tasks, add a trailing todo to sweep Team Context & Decisions until Unrecorded: 0 pending · Unclarified: 0 drafts (a draft leaves Unclarified only via its clarify skill or an explicit user handoff to a named clarify or execute skill).
  • Session-end: before closing, deliver the clarify prompt naming each captured draft (ID + clarify skill); if the user defers clarify, mark those rows handed off.

Specify skills (/architect-specify, /product-specify, etc.) remain available for interactive deep-dive exploration when you want guided trade-off analysis — but are not required for routine capture.

Failure Handling

  • Missing index + missing records → emit the section heading + _Scope: 0 CDRs · 0 ADRs · 0 PDRs · 0 ChDRs · 0 evals · 0 skills — 0 rows shown._ only — no table — and continue the user's task; never block.
  • Unparseable index rows → skip malformed rows, note the skip count.

Verification

  • Team Context & Decisions emitted with _Scope: N CDRs · A ADRs · P PDRs · C ChDRs · E evals · M skills — J rows shown · Unrecorded: N pending · Unclarified: M captured drafts._ (J = all rows shown; Status=in use rows are accepted records only, decision rows carry a clarify skill).
  • Class boots fired at task start (before todo planning), never deferred; workspace-root fallback engaged when CWD has no local memory.
  • Detected decisions added as table rows with the matching clarify skill.
  • Detected decisions mirrored as task-list todos; trailing ledger-sweep todo added after code-modifying tasks; sweep closed only at Unrecorded: 0 pending · Unclarified: 0 drafts with the session-end clarify prompt delivered.

Unconfigured projects

Invoke team-setup to configure team AI directives for this project.

© tikalk, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in skills/team/team-boot of tikalk/adlc-team-skills.

  • SKILL.md
  • references/decision-capture.md
  • references/manual-fallback.md
  • scripts/boot.ps1
  • scripts/boot.sh

Open the folder on GitHubat commit 2dbed36

Compare with similar skills

Team Boot next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Team Boot compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Team Boot this skilltikalk/adlc-team-skills141—~2.2kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3804 repos~2.4kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0
Domain Modelingbrim-borium/spotify_sdk1665 repos~806Automated safety check: PassApache-2.0
Design Doc MermaidSpillwaveSolutions/design-doc-mermaid1751 repos~5.6kAutomated safety check: PassNone

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    380 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 5 repos~806 tokens
    DevelopmentAuto-check passed
  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    175 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-check passed
  • Learning Opportunities

    DrCatHicks/learning-opportunities

    Facilitates deliberate skill development during AI-assisted coding.

    2.5k GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo
  • Architect Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when ADRs need review, gaps need filling, or ADR status must be approved as Accepted before architecture generation.

    141 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • Change Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when reviewing, accepting, rejecting, or deferring ChDRs mined by change-init, validating inferred decisions against their git and issue evidence before promotion to project…

    141 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Change Init

    tikalk/adlc-team-skills

    A skill your agent uses when you want guided mining of git history, structured change-story clustering, or comprehensive rationale recovery before documenting.

    141 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • Change Publish

    tikalk/adlc-team-skills

    A skill your agent uses when accepted ChDRs are ready for promotion from drafts to project memory at docs/adlc/memory/chdr/ and the boot-facing chdr.md index needs regenerating.

    141 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Evals Analyze

    tikalk/adlc-team-skills

    A skill your agent uses when evaluation results need triage and loop-closing — spec failures route to deterministic checks or context rules, generalization failures to the evaluator backlog.

    141 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Evals Clarify

    tikalk/adlc-team-skills

    A skill your agent uses when draft eval criteria need refining, clustering, and acceptance into the published goldset with an isolated holdout split (goldset.md + goldset.json).

    141 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Team Boot

What does Team Boot do?

A skill your agent uses when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index…. Team Boot is an agent skill from tikalk/adlc-team-skills. Use when a session starts or resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution, CDR index, Class Boots catalog, skills registry — is not yet injected; also fires the session-end friction trigger for CDR/ADR/PDR capture with pending-decision safety nets.

When should I use Team Boot?

Team Boot fits situations like: A session starts; resumes after compaction (auto via the sessionstart and sessioncompact event hooks) and the team AI directives context — constitution; class Boots catalog; skills registry — is not yet injected.

How do I install Team Boot in Claude Code?

Run `npx skills add tikalk/adlc-team-skills --skill team-boot -a claude-code`. Or copy the skill folder (skills/team/team-boot in tikalk/adlc-team-skills) into .claude/skills/team-boot in your project. Claude Code loads it when a task matches its description.

How do I install Team Boot in Codex?

Run `npx skills add tikalk/adlc-team-skills --skill team-boot -a codex`. Or copy the skill folder (skills/team/team-boot in tikalk/adlc-team-skills) into .agents/skills/team-boot in your project. Codex loads it when a task matches its description.

Can I use Team Boot in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tikalk/adlc-team-skills --skill team-boot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-boot, .gemini/skills/team-boot, .github/skills/team-boot and .opencode/skills/team-boot in your project.

What does Team Boot need to run?

Going by SKILL.md and its folder, Team Boot needs PowerShell and a shell for the scripts in its folder. Our summary lists: A Bash shell; PowerShell.

Does Team Boot access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Team Boot safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Team Boot use?

Team Boot is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Team Boot use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 783 tokens, read only when the agent opens those files.

What are the alternatives to Team Boot?

Skills that share tags, products or a category with Team Boot: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Boot?

tikalk (a GitHub organization) maintains it in tikalk/adlc-team-skills, which has 141 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 2026.

Source: tikalk/adlc-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.