Capture
alirezarezvani/claude-skills
Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss.
A skill your agent uses when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future…
MITAuto-check passed
Install Superpowers Learning Workflow
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-learning-workflow --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/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/team-skills/superpowers-learning-workflow .claude/skills/superpowers-learning-workflow && 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 "superpowers-learning-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflow into .claude/skills/superpowers-learning-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-learning-workflow", 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/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflowType 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 SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-learning-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/team-skills/superpowers-learning-workflow .agents/skills/superpowers-learning-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "superpowers-learning-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflow into .agents/skills/superpowers-learning-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-learning-workflow", 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 SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-learning-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/team-skills/superpowers-learning-workflow .cursor/skills/superpowers-learning-workflow && 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 "superpowers-learning-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflow into .cursor/skills/superpowers-learning-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-learning-workflow", 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/SYZ-Coder/superpowers-openspec-team-skills.git --path team-skills/superpowers-learning-workflow--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 SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-learning-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/team-skills/superpowers-learning-workflow .gemini/skills/superpowers-learning-workflow && 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 "superpowers-learning-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflow into .gemini/skills/superpowers-learning-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-learning-workflow", 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 SYZ-Coder/superpowers-openspec-team-skills superpowers-learning-workflowInstalls 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 SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/team-skills/superpowers-learning-workflow .github/skills/superpowers-learning-workflow && 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 "superpowers-learning-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflow into .github/skills/superpowers-learning-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-learning-workflow", 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 SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills superpowers-learning-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/team-skills/superpowers-learning-workflow .opencode/skills/superpowers-learning-workflow && 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 "superpowers-learning-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/superpowers-learning-workflow into .opencode/skills/superpowers-learning-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superpowers-learning-workflow", 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
superpowers-learning-workflow- GitHub stars
- 196
- Token cost
- ~1.2k tokens
- SKILL.md length
- 581 words
- Files
- 5
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future…
- Works in 12 steps: Review the recent work, decisions, and… → Classify what was learned into four… → Add required metadata for durable entries → …
- The user explicitly wants to capture lessons from completed work
- SKILL.md covers Overview, Workflow, When to Use and Outputs, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Superpowers Learning Workflow is an agent skill from SYZ-Coder/superpowers-openspec-team-skills. Use when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future sessions.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `README.md`, `agents/openai.yaml` and `readme_cn.md`).
The repository describes itself as: 一套带有记忆和自学习的harness-team-skills企业级编程技能组合库 针对superpowers+openspec 进行按需组合使用,适用于个人与团队协作进行AI编程. The licence is MIT.
When your agent uses it
- The user explicitly wants to capture lessons from completed work
- Persist durable project knowledge
- Turn repeated patterns into reusable learning notes for future sessions
Example prompts
- “/superpowers-learning-workflow”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- Review the recent work, decisions, and verification evidence.
- Classify what was learned into four buckets
- Add required metadata for durable entries
- If .superpowers-memory/ exists, update
- If .superpowers-memory/ does not exist, tell the user to install the memory scaffold or keep the learning summary in a normal project doc.
- Check whether any backlog item is strong enough to recommend promotion into a checklist, project rule, workflow step, script, or skill…
- Review .superpowers-memory/SESSION_CLOSE_CHECKLIST.md before finishing the learning capture.
- Use scripts/suggest-superpowers-memory-updates.ps1 if it is unclear which memory surfaces should be updated from the current session…
- Prefer scripts/run-superpowers-memory-closeout.ps1 as the standard closeout helper when you want one command to review the checklist, get…
- When memory files were updated, run scripts/validate-superpowers-memory.ps1 and include the result in the summary.
- Use scripts/search-superpowers-memory.ps1 when you need to confirm whether a pattern already exists in durable memory or recent journals.
- Summarize what was learned and what, if anything, should become a future rule, checklist, script, or skill.
What it can do on your machine
Read from SKILL.md and the folder at commit 1426ddc. 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.
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
Superpowers Learning Workflow loads about 1.2k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 581 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 SYZ-Coder/superpowers-openspec-team-skills at commit 1426ddc, republished under its MIT licence (© SYZ-Coder). 581 words, ~1,238 tokens.
Download SKILL.mdSave it as
.claude/skills/superpowers-learning-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- superpowers-learning-workflow
- description
- Use when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future sessions.
Superpowers Learning Workflow
Overview
Use this workflow after meaningful work to capture what should survive the current session. It is a lightweight, repo-owned learning loop inspired by reflective agent systems, but scoped for safe use inside normal project workflows.
This is an explicit opt-in workflow. Do not use it by default. Only use it when the user explicitly asks for this workflow, names this skill, or a repository policy explicitly requires it.
Workflow
- Review the recent work, decisions, and verification evidence.
- Classify what was learned into four buckets:
- durable project facts
- current working state
- session outcome
- reusable method or repeated pitfall
- Add required metadata for durable entries:
idstatusconfidencesourcelast_updatedreview_afterDo not mark an entry asverifiedifsourceis empty.
- If
.superpowers-memory/exists, update:PROJECT_CONTEXT.mdfor durable factsCURRENT_STATE.mdfor active stateDECISIONS.mdfor lasting decisionsKNOWN_FAILURES.mdfor repeated failure patternsVERIFICATION_BASELINE.mdfor trusted verification rulesTEAM_PREFERENCES.mdfor durable team agreementsUSER_PROFILE.mdfor durable user preferences that are not project factsAGENT_NOTES.mdfor durable execution reminders that are not project factssession-journal/for the session summaryLEARNING_BACKLOG.mdfor reusable patterns that may deserve future workflows or skills
- If
.superpowers-memory/does not exist, tell the user to install the memory scaffold or keep the learning summary in a normal project doc. - Check whether any backlog item is strong enough to recommend promotion into a checklist, project rule, workflow step, script, or skill draft.
- Review
.superpowers-memory/SESSION_CLOSE_CHECKLIST.mdbefore finishing the learning capture. - Use
scripts/suggest-superpowers-memory-updates.ps1if it is unclear which memory surfaces should be updated from the current session signals. - Prefer
scripts/run-superpowers-memory-closeout.ps1as the standard closeout helper when you want one command to review the checklist, get update suggestions, and optionally run validation. - When memory files were updated, run
scripts/validate-superpowers-memory.ps1and include the result in the summary. - Use
scripts/search-superpowers-memory.ps1when you need to confirm whether a pattern already exists in durable memory or recent journals. - Summarize what was learned and what, if anything, should become a future rule, checklist, script, or skill.
Show full SKILL.md (237 more words)Show less
When to Use
- The user explicitly asks to capture lessons from the current session
- The user explicitly names
$superpowers-learning-workflow - The user wants to persist durable knowledge for future sessions
- The user wants to turn repeated patterns into reusable learning notes
- A repository policy explicitly requires reflective capture after meaningful work
Outputs
- Updated
.superpowers-memory/PROJECT_CONTEXT.mdwhen durable facts changed - Updated
.superpowers-memory/CURRENT_STATE.md - Updated
.superpowers-memory/DECISIONS.mdwhen durable decisions changed - Updated
.superpowers-memory/KNOWN_FAILURES.mdwhen repeated failure patterns were identified - Updated
.superpowers-memory/VERIFICATION_BASELINE.mdwhen trusted verification rules changed - Updated
.superpowers-memory/TEAM_PREFERENCES.mdwhen durable team agreements changed - Updated
.superpowers-memory/USER_PROFILE.mdwhen durable user preferences changed - Updated
.superpowers-memory/AGENT_NOTES.mdwhen durable execution reminders changed - New or updated session journal entry
- Updated
.superpowers-memory/LEARNING_BACKLOG.mdfor reusable lessons - Updated
.superpowers-memory/SESSION_CLOSE_CHECKLIST.mdonly as a reference checklist, not as a session log - Memory validation evidence when memory was updated
- Optional memory update suggestion evidence when the suggestion script was used
- Optional closeout helper output when the closeout script was used
- A short summary of what should be remembered next time
Guardrails
- Do not write temporary TODO noise into
PROJECT_CONTEXT.md - Do not turn a one-off fix into a reusable rule without a clear repeated pattern
- Do not auto-edit the skill library itself unless the user explicitly asks for that separate step
- Keep learning notes concise and actionable
- Do not promote a backlog item without enough repeated evidence or cross-session value
- Treat
ready_for_promotionas a higher bar: expect repeated evidence, linked sources, and a reviewable promotion rationale
© SYZ-Coder, 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 in team-skills/superpowers-learning-workflow of SYZ-Coder/superpowers-openspec-team-skills.
- SKILL.md
- README.md
- agents/openai.yaml
- readme_cn.md
- workflow.yaml
Open the folder on GitHubat commit 1426ddc
Compare with similar skills
Superpowers Learning Workflow 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 |
|---|---|---|---|---|---|---|
| Superpowers Learning Workflow this skillSYZ-Coder/superpowers-openspec-team-skills | 196 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Capturealirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| No Explicit Anythedaviddias/Front-End-Checklist | 74k | — | ~565 | Automated safety check: Pass | MIT | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Lesson Memory Recorderrohitg00/agentmemory | 29k | — | ~721 | Automated safety check: Pass | Apache-2.0 | |
| Verification Before Completionforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
No Explicit Any
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing TypeScript files for type safety regressions, during code review of functions that handle external data, or when the codebase has ESLint warnings for…
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
Lesson Memory Recorder
rohitg00/agentmemory
Distills a user correction or hard-won rule into a confidence-weighted lesson that resurfaces automatically before similar future work.
Verification Before Completion
foryourhealth111-pixel/Vibe-Skills
Completion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready.
Verification Before Completion
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
More from SYZ-Coder/superpowers-openspec-team-skills
Superpowers Openspec Superpowers Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already…
Openspec Feature Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding.
Openspec Superpowers Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants an OpenSpec-first path that creates proposal, design, specs, and tasks before handing off to Superpowers execution, verification, and optional…
Superpowers Feature Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven…
Questions about Superpowers Learning Workflow
What does Superpowers Learning Workflow do?
A skill your agent uses when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future…. Superpowers Learning Workflow is an agent skill from SYZ-Coder/superpowers-openspec-team-skills. Use when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future sessions.
When should I use Superpowers Learning Workflow?
Superpowers Learning Workflow fits situations like: the user explicitly wants to capture lessons from completed work; persist durable project knowledge; turn repeated patterns into reusable learning notes for future sessions.
How do I install Superpowers Learning Workflow in Claude Code?
Run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a claude-code`. Or copy the skill folder (team-skills/superpowers-learning-workflow in SYZ-Coder/superpowers-openspec-team-skills) into .claude/skills/superpowers-learning-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Superpowers Learning Workflow in Codex?
Run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a codex`. Or copy the skill folder (team-skills/superpowers-learning-workflow in SYZ-Coder/superpowers-openspec-team-skills) into .agents/skills/superpowers-learning-workflow in your project. Codex loads it when a task matches its description.
Can I use Superpowers Learning Workflow 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 SYZ-Coder/superpowers-openspec-team-skills --skill superpowers-learning-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superpowers-learning-workflow, .gemini/skills/superpowers-learning-workflow, .github/skills/superpowers-learning-workflow and .opencode/skills/superpowers-learning-workflow in your project.
What does Superpowers Learning Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Superpowers Learning Workflow is instructions for the agent only.
Does Superpowers Learning Workflow 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 Superpowers Learning Workflow 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 Superpowers Learning Workflow use?
Superpowers Learning Workflow 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 Superpowers Learning Workflow use?
About 1.2k tokens (SKILL.md is roughly 5k 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 Superpowers Learning Workflow?
Skills that share tags, products or a category with Superpowers Learning Workflow: Capture (alirezarezvani/claude-skills, 28k stars), No Explicit Any (thedaviddias/Front-End-Checklist, 74k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars) and Lesson Memory Recorder (rohitg00/agentmemory, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Superpowers Learning Workflow?
SYZ-Coder (a GitHub user) maintains it in SYZ-Coder/superpowers-openspec-team-skills, which has 196 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 12, 2026.
Source: SYZ-Coder/superpowers-openspec-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.