Eu AI Act Readiness
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
A skill your agent uses when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Install Planning Mode
$ npx skills add openteams-lab/openteams --skill planning-mode -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openteams-lab/openteams planning-mode --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/planning-mode .claude/skills/planning-mode && rm -rf skills-srcUse ~/.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/
Install the "planning-mode" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-mode into .claude/skills/planning-mode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mode", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-modeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openteams-lab/openteams --skill planning-mode -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openteams-lab/openteams planning-mode --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .agents/skills && cp -r skills-src/assets/skills/planning-mode .agents/skills/planning-mode && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning-mode" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-mode into .agents/skills/planning-mode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mode", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openteams-lab/openteams --skill planning-mode -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openteams-lab/openteams planning-mode --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/assets/skills/planning-mode .cursor/skills/planning-mode && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "planning-mode" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-mode into .cursor/skills/planning-mode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mode", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openteams-lab/openteams.git --path assets/skills/planning-mode--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openteams-lab/openteams --skill planning-mode -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openteams-lab/openteams planning-mode --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/assets/skills/planning-mode .gemini/skills/planning-mode && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "planning-mode" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-mode into .gemini/skills/planning-mode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mode", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openteams-lab/openteams planning-modeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openteams-lab/openteams --skill planning-mode -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .github/skills && cp -r skills-src/assets/skills/planning-mode .github/skills/planning-mode && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "planning-mode" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-mode into .github/skills/planning-mode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mode", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openteams-lab/openteams --skill planning-mode -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openteams-lab/openteams planning-mode --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openteams-lab/openteams.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/assets/skills/planning-mode .opencode/skills/planning-mode && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "planning-mode" agent skill from https://github.com/openteams-lab/openteams/tree/main/assets/skills/planning-mode into .opencode/skills/planning-mode/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning-mode", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
planning-mode- GitHub stars
- 628
- Token cost
- ~1.6k tokens
- SKILL.md length
- 724 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
- Works in 12 steps: Goal Contract → WBS → Dependency Mapping → …
- The user asks to break down a goal into a clear
- SKILL.md covers Purpose, Core Responsibility, Important Constraints and Required Planning Process, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Planning Mode is an agent skill from openteams-lab/openteams. Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management and Legal risk assessment. The repository describes itself as: Plan, Build, and Ship — with a team of AI agents instead of one. The licence is Apache-2.0.
When your agent uses it
- The user asks to break down a goal into a clear
- Reviewable task plan using WBS
Example prompts
- “/planning-mode”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit ebee9de. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Planning Mode loads about 1.6k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 724 words of instructions outside code blocks.
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); files beside SKILL.md are not scanned.
SKILL.md
The full file from openteams-lab/openteams at commit ebee9de, republished under its Apache-2.0 licence (© openteams-lab). 724 words, ~1,585 tokens.
Download SKILL.mdSave it as
.claude/skills/planning-mode/SKILL.md (or your agent's skills folder).- name
- planning-mode
- description
- Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Planning Mode Skill
Purpose
Use this skill to help the user turn a goal into a clear, executable, and reviewable task plan.
This skill is for planning only. It must not perform implementation work, execute tasks, write production code, modify files, call external systems, or complete the planned work.
Core Responsibility
You are in Planning Mode.
Your task is to help the user decompose a goal into a clear, executable, and reviewable task plan.
You must use the following project planning methods:
- WBS: Work Breakdown Structure
- Dependency Mapping: task dependency analysis
- Milestone Plan: milestone planning
- RACI: responsibility assignment
- Risk Register: risk tracking
- Plan Review: planning quality review
Important Constraints
You must follow these constraints:
- You may only design the solution and task plan.
- You must not do any implementation work.
- If the user request is unclear, ask at most 5 key clarification questions.
- If the user wants you to continue directly, proceed with reasonable assumptions and explicitly list those assumptions.
- Every task must have a clear output.
- Do not create vague tasks such as:
- "handle this"
- "optimize this"
- "follow up"
- "improve things"
- "coordinate"
- Break work down by deliverables first, then into work packages, then into concrete tasks.
- Each task should include, where possible:
- task name
- output
- acceptance criteria
- dependencies
- owner role
- priority
- Do not output a loose to-do list.
- Always produce a structured plan.
- At the end, perform a plan review and identify:
- risks
- gaps
- unrealistic assumptions
- decisions requiring user confirmation
Required Planning Process
You must follow this process strictly.
Step 1. Goal Contract
Clarify:
- goal
- success criteria
- scope
- constraints
- assumptions
Step 2. WBS
Create a Work Breakdown Structure based on deliverables:
- Level 1: major deliverables
- Level 2: work packages
- Level 3: concrete tasks
Each concrete task must have a verifiable output.
Step 3. Dependency Mapping
Identify:
- prerequisite dependencies
- parallelizable tasks
- blockers
- critical path
Step 4. Milestone Plan
Organize tasks into phases and milestones.
Each milestone must include acceptance criteria.
Step 5. RACI
Assign responsibility for key tasks:
- R = Responsible: person or role doing the work
- A = Accountable: person or role ultimately responsible
- C = Consulted: person or role providing input
- I = Informed: person or role kept updated
If no real people are provided, use role placeholders such as:
- User
- Lead Agent
- Research Agent
- Review Agent
- Execution Agent
- Domain Expert
- Stakeholder
Step 6. Risk Register
Identify risks with:
- risk description
- probability
- impact
- trigger signal
- mitigation plan
- fallback plan
Step 7. Plan Review
Review whether the plan is:
- goal-clear
- measurable
- output-driven
- dependency-aware
- realistic in scope and sequencing
- clear in ownership
- risk-aware
- actionable
Show full SKILL.md (287 more words)Show less
Required Final Output Format
The final response must include exactly these top-level sections:
# 1. Goal Contract
# 2. WBS Work Breakdown Structure
# 3. Dependency Mapping
# 4. Milestone Plan
# 5. RACI Responsibility Assignment
# 6. Risk RegisterRecommended Output Details
1. Goal Contract
Include:
- Goal
- Success Criteria
- Scope In
- Scope Out
- Constraints
- Assumptions2. WBS Work Breakdown Structure
Use a nested structure:
## Deliverable 1: ...
### Work Package 1.1: ...
- Task:
- Output:
- Acceptance Criteria:
- Dependencies:
- Owner Role:
- Priority:3. Dependency Mapping
Use a table:
| Task | Depends On | Dependency Type | Reason |
|---|---|---|---|Also include:
## Critical Path
...
## Parallelizable Tasks
...
## Blockers
...4. Milestone Plan
Use a table:
| Milestone | Included Tasks | Acceptance Criteria | Estimated Time |
|---|---|---|---|If no calendar dates are provided, use relative time such as Day 1, Week 1, or Phase 1.
5. RACI Responsibility Assignment
Use a table:
| Task / Deliverable | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|6. Risk Register
Use a table:
| Risk | Probability | Impact | Trigger | Mitigation | Fallback |
|---|---|---|---|---|---|Quality Bar
A good plan must satisfy all of the following:
- The goal is clear.
- Success criteria are measurable.
- Scope boundaries are explicit.
- Every major deliverable is represented.
- Every task has a concrete output.
- Tasks are not vague.
- Dependencies are visible.
- Milestones have acceptance criteria.
- Time estimates are realistic or explicitly assumption-based.
- RACI ownership is clear.
- Risks include mitigation and fallback.
- The plan ends with exactly 3 next actions.
Failure Modes to Avoid
Avoid these failures:
- Creating only a simple checklist.
- Skipping WBS and jumping directly to a task list.
- Giving tasks without outputs.
- Giving tasks without acceptance criteria.
- Inventing precise dates without user-provided dates.
- Assigning fake people when role placeholders would be better.
- Ignoring risk.
- Forgetting to perform plan review.
- Doing implementation work.
- Asking too many clarification questions.
If Information Is Missing
MUST Ask Clarifying Questions, Ask at most 5 questions.
Use this when the missing information would materially change the plan.
Implementation Boundary
This skill must never execute the plan.
Allowed:
- clarify requirements
- discuss solution details
- generate plan
- decompose tasks
- identify dependencies
- assign roles
- identify risks
- review plan
Not allowed:
- implement tasks
- write production code
- edit files
- call deployment tools
- complete user work
- mark planned tasks as actually done without evidence
© openteams-lab, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in assets/skills/planning-mode of openteams-lab/openteams.
Open the folder on GitHubat commit ebee9de
Compare with similar skills
Planning Mode 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Planning Mode this skillopenteams-lab/openteams | 628 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Eu AI Act Readinessseb1n/awesome-ai-agent-skills | 206 | — | ~3.3k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Uvastral-sh/claude-code-plugins | 313 | 2 repos | ~980 | Automated safety check: Pass | Apache-2.0 | |
| Project Managementkunchenguid/firstmate | 7.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Hivemind Goalsactiveloopai/hivemind | 1.6k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 |
Similar skills
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
- Official
Uv
astral-sh/claude-code-plugins
Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.
Project Management
kunchenguid/firstmate
Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.
Hivemind Goals
activeloopai/hivemind
Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.
Ichartjs
wanghetommy/ichartjs
Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.
More from openteams-lab/openteams
Brainstorming
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
Code Guidelines
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
GitHub Actions Run And Fix
openteams-lab/openteams
OpenTeams skill for manually starting a GitHub Actions workflow, watching its execution, diagnosing failures, rerunning transient failed jobs, repairing code or configuration errors, and dispatching…
GitHub PR Actions Fix
openteams-lab/openteams
OpenTeams skill for watching GitHub Actions checks after a pull request is submitted or updated, inspecting failures, making the smallest safe code fix, validating locally, pushing to the PR branch…
Using Git Worktrees
openteams-lab/openteams
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git…
Writing Plans
openteams-lab/openteams
OpenTeams-only workflow skill. An agent skill from openteams-lab/openteams.
Related
Categories
Questions about Planning Mode
What does Planning Mode do?
A skill your agent uses when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review. Planning Mode is an agent skill from openteams-lab/openteams. Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
When should I use Planning Mode?
Planning Mode fits situations like: the user asks to break down a goal into a clear; reviewable task plan using WBS.
How do I install Planning Mode in Claude Code?
Run `npx skills add openteams-lab/openteams --skill planning-mode -a claude-code`. Or copy the skill folder (assets/skills/planning-mode in openteams-lab/openteams) into .claude/skills/planning-mode in your project. Claude Code loads it when a task matches its description.
How do I install Planning Mode in Codex?
Run `npx skills add openteams-lab/openteams --skill planning-mode -a codex`. Or copy the skill folder (assets/skills/planning-mode in openteams-lab/openteams) into .agents/skills/planning-mode in your project. Codex loads it when a task matches its description.
Can I use Planning Mode 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 openteams-lab/openteams --skill planning-mode -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning-mode, .gemini/skills/planning-mode, .github/skills/planning-mode and .opencode/skills/planning-mode in your project.
What does Planning Mode need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning Mode is instructions for the agent only.
Does Planning Mode 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 Planning Mode 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. Review the folder before installing.
What licence does Planning Mode use?
Planning Mode is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Planning Mode use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Planning Mode?
Skills that share tags, products or a category with Planning Mode: Eu AI Act Readiness (seb1n/awesome-ai-agent-skills, 206 stars), CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars) and Project Management (kunchenguid/firstmate, 7.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning Mode?
openteams-lab (a GitHub organization) maintains it in openteams-lab/openteams, which has 628 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.
Source: openteams-lab/openteams on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.