.NET MAUI Release Readiness
dotnet/maui
Produces evidence-backed ship-readiness verdicts for .NET MAUI Servicing Releases and Previews, and drafts public-safe release handoff pages from the result.
Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests.
Install Trace Requirement
$ npx skills add danielvm-git/bigpowers --skill trace-requirement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install danielvm-git/bigpowers trace-requirement --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/danielvm-git/bigpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/trace-requirement .claude/skills/trace-requirement && 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 "trace-requirement" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/trace-requirement into .claude/skills/trace-requirement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-requirement", 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/danielvm-git/bigpowers/tree/main/skills/trace-requirementType 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 danielvm-git/bigpowers --skill trace-requirement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install danielvm-git/bigpowers trace-requirement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/trace-requirement .agents/skills/trace-requirement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trace-requirement" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/trace-requirement into .agents/skills/trace-requirement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-requirement", 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 danielvm-git/bigpowers --skill trace-requirement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install danielvm-git/bigpowers trace-requirement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/trace-requirement .cursor/skills/trace-requirement && 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 "trace-requirement" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/trace-requirement into .cursor/skills/trace-requirement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-requirement", 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/danielvm-git/bigpowers.git --path skills/trace-requirement--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 danielvm-git/bigpowers --skill trace-requirement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install danielvm-git/bigpowers trace-requirement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/trace-requirement .gemini/skills/trace-requirement && 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 "trace-requirement" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/trace-requirement into .gemini/skills/trace-requirement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-requirement", 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 danielvm-git/bigpowers trace-requirementInstalls 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 danielvm-git/bigpowers --skill trace-requirement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/trace-requirement .github/skills/trace-requirement && 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 "trace-requirement" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/trace-requirement into .github/skills/trace-requirement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-requirement", 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 danielvm-git/bigpowers --skill trace-requirement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install danielvm-git/bigpowers trace-requirement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/danielvm-git/bigpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/trace-requirement .opencode/skills/trace-requirement && 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 "trace-requirement" agent skill from https://github.com/danielvm-git/bigpowers/tree/main/skills/trace-requirement into .opencode/skills/trace-requirement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-requirement", 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
trace-requirement- GitHub stars
- 256
- Token cost
- ~625 tokens
- SKILL.md length
- 195 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests.
- Works in 4 steps: Extract story IDs → Search for story tags in code → Build the matrix → …
- You want to verify coverage of a release plan
- SKILL.md covers Pre-flight and Process
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Trace Requirement is an agent skill from danielvm-git/bigpowers. Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITYLATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find "dark" stories with no code.
Its SKILL.md is about 630 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 Feature launches and release readiness. The repository describes itself as: Agent skills synthesizing years of software engineering discipline into a prescriptive methodology for solo developers. The licence is MIT.
When your agent uses it
- You want to verify coverage of a release plan
- Audit which stories are implemented
- Find dark stories with no code
Example prompts
- “/trace-requirement”
Workflow steps
4 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 812d57a. 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
Trace Requirement loads about 625 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 195 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 danielvm-git/bigpowers at commit 812d57a, republished under its MIT licence (© danielvm-git). 195 words, ~625 tokens.
Download SKILL.mdSave it as
.claude/skills/trace-requirement/SKILL.md (or your agent's skills folder).- name
- trace-requirement
- description
- Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Produces specs/TRACEABILITY_LATEST.md. Use when you want to verify coverage of a release plan, audit which stories are implemented, or find "dark" stories with no code.
- model
- haiku
- effort
- standard
Trace Requirement
Build a traceability matrix from specs/release-plan.yaml + epic capsule directories to implementing code and tests. Surfaces gaps in both directions: stories with no code, and code with no story.
Pre-flight
HARD GATE —
specs/release-plan.yaml + epic capsule directoriesmust exist. If it doesn't, runplan-releasefirst.
→ verify: test -f specs/release-plan.yaml && test -d specs/epics
Read specs/release-plan.yaml + epic capsule directories fully before proceeding.
Process
1. Extract story IDs
From release-plan.yaml, collect all story IDs (e.g. 1.1, 1.2, 2.1).
→ verify: grep -rho 'e[0-9]\+s[0-9]\+' specs/release-plan.yaml specs/epics/*/epic.yaml 2>/dev/null | sort -u | head -1 | grep -q .
2. Search for story tags in code
Look for // story: X.Y or # story: X.Y comments in source files and tests:
grep -rn "story: " . --include="*.ts" --include="*.js" --include="*.py" --include="*.sh" | grep -v node_modules→ verify: [ "$(grep -rl "story: " . --include="*.ts" --include="*.sh" --include="*.py" 2>/dev/null | wc -l | tr -d " ")" -gt 0 ]
3. Build the matrix
For each story ID:
- Implemented: list files that contain
// story: X.Y - Tested: list test files that contain
// story: X.Y - Dark: story has no tag in any file — flag as unimplemented
For each tagged file with no matching story ID in release-plan.yaml:
- Orphan: code exists but story was removed or never planned — flag for cleanup
4. Write specs/TRACEABILITY_LATEST.md
## Story Coverage
| Story | Title | Files | Tests | Status |
|-------|--------------------|-------|-------|-----------|
| 1.1 | [title] | 2 | 1 | Covered |
| 1.2 | [title] | 0 | 0 | Dark |
## Orphan Code (no story tag)
- [file]: contains untagged implementation
## Gaps (dark stories)
- Story 1.2: no implementation found → run plan-work
## Coverage summary
Stories: [X] covered / [Y] dark / [Z] total→ verify: grep -c "Covered\|Dark" specs/TRACEABILITY_LATEST.md
Suggest plan-work for each dark story found.
© danielvm-git, MIT. 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 skills/trace-requirement of danielvm-git/bigpowers.
Open the folder on GitHubat commit 812d57a
Compare with similar skills
Trace Requirement 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 |
|---|---|---|---|---|---|---|
| Trace Requirement this skilldanielvm-git/bigpowers | 256 | — | ~625 | Automated safety check: Pass | MIT | |
| .NET MAUI Release Readinessdotnet/maui | 23k | — | ~15k | Automated safety check: Pass | MIT | |
| Release ValidationMesh-LLM/mesh-llm | 3.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Final Release Reviewopenai/openai-agents-python | 30k | — | ~5.4k | Automated safety check: Pass | MIT | |
| Final Release Reviewopenai/openai-agents-js | 3.9k | — | ~4k | Automated safety check: Pass | MIT | |
| Acceptance Demo GeneratorChachamaru127/claude-code-harness | 3.2k | — | ~3.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Release Validation
Mesh-LLM/mesh-llm
A skill your agent uses when validating a MeshLLM release candidate or current HEAD against the last GitHub release, assembling the canonical feature/fix/modification inventory, testing locally…
- Official
Final Release Review
openai/openai-agents-python
Assess a Python SDK release candidate or release plan against the previous release and recommend ship or block.
- Official
Final Release Review
openai/openai-agents-js
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
Acceptance Demo Generator
Chachamaru127/claude-code-harness
Renders a single HTML page showing each acceptance criterion as verified or not, with a ship, wait, or reject recommendation for non-engineers.
Schematic
blader/schematic
Reverse engineer a detailed product and technical specification document from a git branch's implementation.
More from danielvm-git/bigpowers
All 39 skills in this repoExtract Design
danielvm-git/bigpowers
Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.
Align Grid
danielvm-git/bigpowers
Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one.
Assess Impact
danielvm-git/bigpowers
Analyze the blast radius of a proposed change before any code is written.
Audit Code
danielvm-git/bigpowers
Self-review checklist for the coding agent to run before dispatching a reviewer.
Audit Plan
danielvm-git/bigpowers
Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins.
Compose Workflow
danielvm-git/bigpowers
Chain multiple bigpowers skills into a custom workflow recipe saved in specs/.
Related
Categories
Questions about Trace Requirement
What does Trace Requirement do?
Link story IDs from specs/release-plan.yaml + epic capsule directories to the implementing code and tests. Trace Requirement is an agent skill from danielvm-git/bigpowers.yaml + epic capsule directories to the implementing code and tests.
When should I use Trace Requirement?
Trace Requirement fits situations like: you want to verify coverage of a release plan; audit which stories are implemented; find dark stories with no code.
How do I install Trace Requirement in Claude Code?
Run `npx skills add danielvm-git/bigpowers --skill trace-requirement -a claude-code`. Or copy the skill folder (skills/trace-requirement in danielvm-git/bigpowers) into .claude/skills/trace-requirement in your project. Claude Code loads it when a task matches its description.
How do I install Trace Requirement in Codex?
Run `npx skills add danielvm-git/bigpowers --skill trace-requirement -a codex`. Or copy the skill folder (skills/trace-requirement in danielvm-git/bigpowers) into .agents/skills/trace-requirement in your project. Codex loads it when a task matches its description.
Can I use Trace Requirement 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 danielvm-git/bigpowers --skill trace-requirement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trace-requirement, .gemini/skills/trace-requirement, .github/skills/trace-requirement and .opencode/skills/trace-requirement in your project.
What does Trace Requirement need to run?
SKILL.md names no scripts, command-line tools or credentials: Trace Requirement is instructions for the agent only.
Does Trace Requirement 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 Trace Requirement 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 Trace Requirement use?
Trace Requirement 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 Trace Requirement use?
About 625 tokens (SKILL.md is roughly 2.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 Trace Requirement?
Skills that share tags, products or a category with Trace Requirement: .NET MAUI Release Readiness (dotnet/maui, 23k stars), Release Validation (Mesh-LLM/mesh-llm, 3.5k stars), Final Release Review (openai/openai-agents-python, 30k stars) and Final Release Review (openai/openai-agents-js, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trace Requirement?
danielvm-git (a GitHub user) maintains it in danielvm-git/bigpowers, which has 256 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on September 21, 2026.
Source: danielvm-git/bigpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.