Agent skill

Workspace

by tikalk in tikalk/adlc-team-skills

A skill your agent uses when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA…

MITAuto-check passedDevelopment

Install Workspace

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

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

GitHub CLI
$ gh skill install tikalk/adlc-team-skills workspace --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/workspace .claude/skills/workspace && 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
workspace
GitHub stars
141
Used in
1 other repo
Token cost
~3.7k tokens
SKILL.md length
1,392 words
Files
6 (incl. scripts)
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA…

  • Works in 5 steps: .adlc/ Structure Creation → .gitignore Configuration → Child Repo Discovery → …
  • Coordinating a multi-repo workspace — init the .adlc/ structure
  • SKILL.md covers Overview, When to Use, User Input and Commands, plus 11 more sections
  • Runs Shell and PowerShell scripts from its folder; calls git

What it does

Workspace is an agent skill from tikalk/adlc-team-skills. Use when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA drift).

Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts (for example `scripts/bash/paths.sh`, `scripts/bash/setup-workspace.sh` and `scripts/bash/workspace.sh`).

It sits in Development. It works with Git. 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

  • Coordinating a multi-repo workspace — init the .adlc/ structure
  • Discover and link child repos as submodules
  • Audit workspace health (branch

Example prompts

  • “/workspace”

Requirements

  • A Bash shell
  • PowerShell

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. .adlc/ Structure Creation
  2. .gitignore Configuration
  3. Child Repo Discovery
  4. Child Repo Action (optional)
  5. Output Summary

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 5 files in scripts/ (Shell and PowerShell), which the agent can run.

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Workspace loads about 3.7k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 1,392 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~3.7k

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,392 words, ~3,686 tokens.

Download SKILL.mdSave it as .claude/skills/workspace/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
workspace
description
Use when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA drift).

workspace

Overview

A multi-repo workspace coordinator for shared team context. The parent repository holds shared decisions (PDRs, ADRs, CDRs) under .adlc/, created by product-specify, architect-specify, and team-levelup. Child implementation repositories are discovered at depth 1 and optionally linked as Git submodules so the entire workspace can be cloned with git clone --recursive.

No workspace.yml, no registry file. Pure convention:

  • Parent repo = current working directory (must be a Git repo)
  • Child repos = depth-1 subdirectories containing .git/
  • Shared context = .adlc/ in parent root

When to Use

  • First-time setup (--init): Create .adlc/ directory structure, configure .gitignore conventions, and optionally link child repos.
  • After product-specify or architect-specify has created shared PDRs/ADRs in the parent repo and you have multiple implementation repos alongside.
  • When you've cloned new child repos into the workspace and want to register them as submodules (--link) or ignore them (--ignore-only).
  • To audit workspace health: dirty working trees, unpushed commits, SHA drift between parent submodule reference and child HEAD.
  • To verify child repos can see the parent .adlc/ shared context.
When NOT to Use --init
  • Workspace already initialized: Use /workspace --status to audit instead.
  • Only auditing child repo state: Use /workspace (read-only discovery + status).
  • Linking additional child repos after init: Use /workspace --link directly.

User Input

text
$ARGUMENTS

Commands

CommandPurpose
/workspace --initInitialize: create .adlc/ structure, configure .gitignore, discover child repos
/workspaceDiscover child repos, show summary status (read-only)
/workspace --linkConvert child repos to Git submodules (requires clean parent tree)
/workspace --statusDetailed audit: branch, dirty, unpushed, SHA drift, .adlc presence
/workspace --ignore-onlyAdd child repos to .gitignore instead of creating submodules
/workspace --init --linkInitialize + link child repos in one step
/workspace --init --ignore-onlyInitialize + add child repos to .gitignore
/workspace --dry-runPreview changes without executing (combine with --init, --link, --ignore-only)
/workspace --forceConvert repos already tracked by parent index (requires clean tree)

Execution

Init Mode (--init)

Run the init setup script to create .adlc/ structure, check .gitignore conventions, and discover child repos:

bash
# Bash
scripts/bash/setup-workspace.sh --json

# PowerShell
scripts/powershell/setup-workspace.ps1

Init setup output (JSON):

json
{
  "REPO_ROOT": "/path/to/parent",
  "ADLC_DIR": "/path/to/parent/.adlc",
  "ADLC_DIRS_CREATED": [".adlc/product", ".adlc/drafts", ".adlc/drafts/pdr"],
  "GITIGNORE_EXISTS": true,
  "GITIGNORE_RULES_MISSING": [".adlc/"],
  "CHILD_REPOS": [
    {"name": "backend-api", "path": "/path/to/parent/backend-api", "remote": "git@github.com:org/backend-api.git", "is_submodule": false, "is_tracked": false}
  ],
  "CHILD_COUNT": 1,
  "BRANCH": "main"
}

Directories created:

.adlc/
├── product/           # PDRs (product-specify, product-init)
├── architecture/      # ADRs (architect-specify, architect-init)
├── context/           # CDRs (team-levelup, team-init)
├── skills/            # Team skills metadata
└── drafts/            # Draft artifacts before clarification
    ├── pdr/
    ├── adr/
    ├── cdr/
    ├── skills/
    └── evals/

After init setup, if --link or --ignore-only is also specified, proceed to the corresponding action mode below.

Run the workspace coordinator script:

bash
# Bash
"$(dirname "$0")/../scripts/bash/workspace.sh" --json [--link] [--status] [--dry-run] [--force] $ARGUMENTS

Parse the JSON output and present it to the user.

Output Contract

Init Mode Output

Emitted by setup-workspace.sh --json (see above).

Emitted by workspace.sh --json:

json
{
  "PARENT_REPO": "/abs/path/to/parent",
  "PARENT_BRANCH": "main",
  "PARENT_HAS_ADLC": true,
  "MODE": "discover|link|status",
  "DRY_RUN": false,
  "DISCOVERED_COUNT": 3,
  "REGISTERED_COUNT": 2,
  "SKIPPED_COUNT": 1,
  "ERROR_COUNT": 0,
  "REPOS": [
    {
      "name": "backend-api",
      "path": "/abs/path/to/parent/backend-api",
      "remote": "git@github.com:org/backend-api.git",
      "branch": "main",
      "dirty": false,
      "unpushed": 0,
      "is_submodule": true,
      "parent_sha": "abc1234",
      "child_sha": "abc1234",
      "sha_drift": false,
      "has_adlc": false
    }
  ],
  "ERRORS": []
}

Init Phases

Phase 1: .adlc/ Structure Creation

The setup script creates the .adlc/ directory tree if it doesn't exist (product/, drafts/, and the per-family draft subdirectories — ADR-401 scopes .adlc/ to machine pipeline state). This is the shared context directory where other skills write drafts and pipeline state; published decision records and compiled deliverables live under docs/adlc/.

Idempotent: already-existing directories are not recreated.

Phase 2: .gitignore Configuration

The setup script checks .gitignore for workspace conventions and reports missing rules.

Allowlist model (ADR-401 R7) — .adlc/ is no longer ignored wholesale. Machine pipeline state is ignored via .adlc/* with tracked exceptions re-included; published content under docs/adlc/ is always tracked:

gitignore
# agent-install surface (regenerated)
.agents/
.opencode/
.claude/
.cursor/
.codex/
.gemini/
.qwen/
.devin/
.tabnine/
skills-lock.json
.skills.json
.mcp.json
.events.json
.pytest_cache/
.ruff_cache/

# machine pipeline + runtime state (tracked exceptions follow)
.adlc/*
!.adlc/init-options.json
!.adlc/workspace.yml
!.adlc/drafts/
!.adlc/evals/
.adlc/evals/results/
!.adlc/memory/
.adlc/memory/*
!.adlc/memory/evals/
!.adlc/memory/evals/holdout.json

# generated reports (legacy name kept during transition)
.adlc/team-learn-report.md
.adlc/team-levelup-report.md

# knowledge graph (generated)
graphify-out/

The allowlist has a single definition in scripts/bash/paths.sh (GITIGNORE_RULES_ALLOWLIST, mirrored in scripts/powershell/paths.ps1); the setup scripts source it and report any missing rules. Tracked legacy files keep working — gitignore gates only untracked files.

Action: If GITIGNORE_RULES_MISSING is non-empty, add the missing rules to .gitignore. Do NOT remove existing rules. If changes were made and not in --dry-run mode, commit with message [workspace] Configure .gitignore for workspace conventions.

Phase 3: Child Repo Discovery

Review discovered child repos from setup output.

Present discovered repos:

markdown
## Discovered Child Repos

| # | Repo | Remote | Submodule? | Tracked? |
|---|------|--------|------------|----------|
| 1 | **backend-api** | git@github.com:org/backend-api.git | No | No |
| 2 | **frontend** | git@github.com:org/frontend.git | Yes | N/A |

Reply: Y to proceed with --link/--ignore-only, or adjust.
Phase 4: Child Repo Action (optional)

If --link or --ignore-only is combined with --init, execute the corresponding action after init setup.

Delegates to workspace.sh --link. Safety checks enforced:

  • Parent working tree must be clean (no uncommitted changes outside child repos)
  • Child repos must have a remote origin URL configured
  • Already-registered submodules are skipped (idempotent)
  • Repos tracked in parent index require --force
--ignore-only (Ignore Instead of Submodule)

Add each discovered child repo to .gitignore instead of creating submodules.

For each child repo:

  1. If tracked in parent index: git rm --cached <name> (remove from index, keep on disk)
  2. Add <name>/ to .gitignore if not already present
  3. Skip repos already in .gitignore (idempotent)

Commit with message [workspace] Add child repos to .gitignore if changes were made.

Use when: Child repos are truly independent projects; team members manage them separately.

Phase 5: Output Summary
markdown
## Workspace Init Complete

### .adlc/ Structure
- Created: 7 directories under `.adlc/` (`product/`, `drafts/`, `drafts/{pdr,adr,cdr,skills,evals}/`)

### .gitignore
- Rules added: 5
- Rules verified: 12

### Child Repos
- Discovered: 3
- Registered as submodules: 2
- Ignored: 0
- Skipped (already submodules): 1

### Next Steps
1. Create product decisions: `/product-specify`
2. Create architecture decisions: `/architect-specify`
3. Audit workspace health: `/workspace --status`

Discovery Rules

RuleBehavior
Depth1 level only (direct subdirectories of parent root)
DetectionDirectory contains .git/ directory or .git file
Exclusionsnode_modules, .venv, venv, dist, build, target, .idea, .vscode, .git, .cache, .specify
No config fileNo workspace.yml — pure auto-discovery

Shared Team Context (.adlc/)

The parent repo's .adlc/ directory is the single source of truth for team context. It is created by --init and maintained by other skills:

ArtifactPathCreated By
PDR drafts.adlc/drafts/pdr/ (accepted → docs/adlc/memory/pdr/)product-specify, product-init
ADR drafts.adlc/drafts/adr/ (accepted → docs/adlc/memory/adr/)architect-specify, architect-init
CDRsteam-ai-directives adlc branch (local drafts in .adlc/drafts/cdr/)team-levelup, team-init
Skillsagent skills dir (.agents/skills/ mirror)team-skills
Directory structure.adlc/ treeworkspace --init (this skill)

In audit mode (default), this skill does not create or modify .adlc/ content. It only:

  1. Verifies the parent has .adlc/ (warns if missing).
  2. Checks whether each child repo has its own .adlc/ (informational).
Show full SKILL.md (529 more words)Show less

Safety

  • --init is safe: Only creates directories and reports missing .gitignore rules; never overwrites existing content.
  • .gitignore changes are additive: Only adds missing rules; never removes existing rules.
  • Read-only by default: /workspace and /workspace --status make no changes.
  • --link requires clean parent tree: uncommitted changes outside child repos abort the operation.
  • --force removes child directories from the parent Git index (git rm --cached) before re-adding as submodules. Requires a clean working tree.
  • Idempotent: already-registered submodules, already-ignored repos, and already-created directories are skipped on re-run.
  • Child repos without a remote origin are reported as errors and skipped during --link.
  • --dry-run previews all changes without executing.

Common Rationalizations

RationalizationWhy it's wrongDo this instead
"I'll create .adlc/ manually with mkdir"Misses the full directory tree and .gitignore conventionsRun --init for complete initialization
"I'll add workspace.yml for explicit repo list"Adds config overhead; auto-discovery is simpler and sufficientUse depth-1 discovery; exclude via .gitignore if needed
"I'll skip the .gitignore setup"Risks committing local agent state (.agents/, .opencode/)Let --init configure conventions
"I'll create .adlc/ in child repos too"Diverges from single-source-of-truth modelKeep .adlc/ in parent only; children reference parent
"I'll skip the clean-tree check for --link"Risks losing uncommitted parent changesRequire clean tree; tell user to commit or stash first
"I'll use worktrees instead of submodules"Worktrees are for feature isolation, not multi-repo coordinationUse submodules for tracked multi-repo linking
"I'll use --ignore-only instead of submodules for everything"Loses workspace coordination benefitsUse --link for tracked repos; --ignore-only only for independent projects

Red Flags

  • Running --link without checking parent working tree is clean.
  • Running --force on a parent with uncommitted changes outside child repos.
  • Creating .adlc/ content in child repos (parent is the single source).
  • Adding a workspace.yml or registry file (convention-only, no config).
  • Re-including .specify in discovery — the scripts hard-exclude it (see Discovery Rules), and that exclusion is intentional.
  • Modifying child repo contents during --link (only parent index changes).
  • Skipping .gitignore setup when local agent directories exist.

Verification

  • Parent repo is a Git repository.
  • --init creates .adlc/ with its subdirectories (product/, drafts/, drafts/{pdr,adr,cdr,skills,evals}/).
  • --init reports missing .gitignore rules (additive, never removes).
  • --init is idempotent (second run reports 0 dirs created).
  • Parent .adlc/ exists (warn if missing in audit mode).
  • Child repos discovered at depth 1 (excluding node_modules, .venv, etc.).
  • --link only runs when parent working tree is clean.
  • Already-registered submodules are skipped (idempotent).
  • Child repos without origin remote are reported as errors.
  • --status reports branch, dirty state, unpushed count, SHA drift, .adlc presence per child.
  • --ignore-only adds repos to .gitignore and removes from parent index.
  • --dry-run produces no file changes.
  • JSON output matches the Output Contract schema for both init and audit modes.

Integration with Existing Skills

SkillRelationship
product-specifyCreates PDR drafts in parent .adlc/drafts/pdr/ after --init
architect-specifyCreates ADR drafts in parent .adlc/drafts/adr/ after --init
team-levelupCreates CDR drafts (published to the team-ai-directives adlc branch) after --init
team-bootLoads parent .adlc context at session start
team-setupConfigures agent directories (.agents/, .opencode/) — complement to --init

12-Factor Alignment

Factor XI (Directives as Code) — establishes a version-controlled multi-repo workspace where shared decisions live in the parent and implementation repos are linked as submodules or ignored by convention.

© 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 5 other files (scripts) in skills/team/workspace of tikalk/adlc-team-skills.

  • SKILL.md
  • scripts/bash/paths.sh
  • scripts/bash/setup-workspace.sh
  • scripts/bash/workspace.sh
  • scripts/powershell/paths.ps1
  • scripts/powershell/setup-workspace.ps1

Open the folder on GitHubat commit 2dbed36

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in tikalk/adlc-team-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Workspace 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.

Workspace compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workspace this skilltikalk/adlc-team-skills1411 repos~3.7kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything86k1 repos~1.2kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Understand Diff AnalysisEgonex-AI/Understand-Anything86k1 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Codebase Knowledge Graph Q&A

    Egonex-AI/Understand-Anything

    Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.

    86k GitHub starsUsed in 1 repo~1.2k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub starsUsed in 1 repo~1.4k tokens
    DevelopmentAuto-check passed
  • Understand Explain

    Egonex-AI/Understand-Anything

    Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.

    86k GitHub starsUsed in 1 repo~1.3k tokens
    DevelopmentAuto-check passed

More from tikalk/adlc-team-skills

All 44 skills in this repo
  • Team Boot

    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…

    141 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed
  • 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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    Auto-check passed

Works with

Categories

Questions about Workspace

What does Workspace do?

A skill your agent uses when coordinating a multi-repo workspace — init the .adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA…. Workspace is an agent skill from tikalk/adlc-team-skills.adlc/ structure, discover and link child repos as submodules, or audit workspace health (branch, dirty, unpushed, SHA drift).

When should I use Workspace?

Workspace fits situations like: coordinating a multi-repo workspace — init the .adlc/ structure; discover and link child repos as submodules; audit workspace health (branch.

How do I install Workspace in Claude Code?

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

How do I install Workspace in Codex?

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

Can I use Workspace 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 workspace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workspace, .gemini/skills/workspace, .github/skills/workspace and .opencode/skills/workspace in your project.

What does Workspace need to run?

Going by SKILL.md and its folder, Workspace needs a shell and PowerShell for the scripts in its folder and the command-line tools its instructions call (git). Our summary lists: A Bash shell; PowerShell.

Does Workspace access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Workspace 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 Workspace use?

Workspace 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 Workspace use?

About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workspace?

Skills that share tags, products or a category with Workspace: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workspace?

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.