executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
portfolioAggregate cross-repo issue/MR/CI health across vault-registered projects into a single Markdown dashboard
Independent GitHub snapshot · Automated classification · Original documentation governs
Read skills/portfolio/SKILL.md in full before taking any action, then follow its complete workflow.
The linked document is authoritative, including its prechecks, argument rules, and stop conditions.
Resolve this link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as skills/ and scripts/ from that root; resolve relative links inside the canonical document from its own directory. Keep the user’s project as the target of project operations.
$ARGUMENTS means the trailing user input after the selected command skill, or an empty string when absent. Preserve flags, quoted text, and Unicode as data. Do not perform global substitution in the command document, shell expansion on the argument string, or execution of that string as shell code. When the workflow needs a command, pass its arguments through structured tool parameters or safely quoted individual arguments.
Regenerate with node scripts/generate-codex-skills.mjs.