agentleFS
Luis85Luis85/agentic-workflow/.claude/skills/portfolio-track/SKILL.md

portfolio-track

Skill0 starsChanged 6 months agoMITView on GitHub

Drive P5 Express portfolio cycle. Detects which cycle (X strategy / Y monthly / Z daily) is due, dispatches /portfolio:x|y|z. Triggers "run portfolio review", "portfolio cycle", "portfolio health". Opt-in.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 2 are distinctive, and 11 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is "list", print the table below and exit (do not dispatch any cycle):

    line 27
  2. Very specific:

    If no portfolio/ directory exists, output:

    line 34
  3. Very specific:

    If more than one portfolio has status: active, use AskUserQuestion to ask which one to manage.

    line 43
  4. Very specific:

    If only one active portfolio exists, select it automatically and note it to the user.

    line 44
  5. Very specific:

    If the slug was provided as $ARGUMENTS and it matches an existing portfolio, use it directly.

    line 45
  6. Distinctive:

    When multiple cycles are overdue, recommend the highest-cadence one first (X > Y > Z), but note the others.

    line 59
  7. Very specific:

    Run the selected /portfolio:<x|y|z> command with the portfolio slug as argument.

    line 70
  8. Very specific:

    After the command completes, read portfolio/<slug>/portfolio-state.md and print a status block:

    line 76
  9. Very specific:

    Never run a cycle without user confirmation — always gate through AskUserQuestion.

    line 93
  10. Very specific:

    Never edit portfolio artifacts directly — the /portfolio:* commands own those files.

    line 94
  11. Very specific:

    Never modify specs/ artifacts — portfolio track is read-only on the Specorator side.

    line 95
  12. Distinctive:

    Never recommend skipping the Portfolio Sponsor review for stop/start decisions — surface them as "Decisions required from Sponsor" and stop.

    line 96
  13. Very specific:

    If portfolio-definition.md is missing, stop and tell the user to run /portfolio:start first.

    line 97

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Portfolio Track

You are the conductor of the P5 Express portfolio management cadence defined in docs/portfolio-track.md. Your job is to detect the right cycle, confirm with the user, and dispatch — never to do the cycle work yourself. The /portfolio:* commands spawn the portfolio-manager subagent; you only read state, ask, and hand off.

Shared rules (gating, escalation, constraints common to all conductors): ../_shared/conductor-pattern.md.

Read first

  • docs/portfolio-track.md — full methodology and cycle descriptions.
  • memory/constitution.md — governing principles.

Step 1 — Detect portfolio(s)

Scan for portfolio/*/portfolio-state.md files. For each found, read its YAML frontmatter and extract:

  • portfolio (slug)
  • status (active | paused | done)
  • last_x, last_y, last_z (ISO dates or null)

If $ARGUMENTS is "list", print the table below and exit (do not dispatch any cycle):

Portfolio           Status    last_x        last_y        last_z
<slug>              active    <date|never>  <date|never>  <date|never>

If no portfolio/ directory exists, output:

No portfolio found. Run /portfolio:start <slug> to bootstrap one, then come back here.

Exit without dispatching.


Step 2 — Pick a portfolio (if multiple active)

If more than one portfolio has status: active, use AskUserQuestion to ask which one to manage. If only one active portfolio exists, select it automatically and note it to the user. If the slug was provided as $ARGUMENTS and it matches an existing portfolio, use it directly.


Step 3 — Recommend the due cycle

Calculate days since each cycle was last run (use today's date from # currentDate in context, or ask if unavailable):

ConditionRecommendation
last_x is null or ≥ 180 days ago/portfolio:x — 6-monthly strategic review due
last_y is null or ≥ 30 days ago/portfolio:y — monthly tactical review due
Neither of the above/portfolio:z — daily operations check

When multiple cycles are overdue, recommend the highest-cadence one first (X > Y > Z), but note the others.

Present the recommendation plus all three as selectable alternatives. Use a single AskUserQuestion:

"Portfolio <slug> — recommended cycle: <X/Y/Z> (<reason>). Options: X (6-monthly strategy) · Y (monthly review) · Z (daily ops) · Cancel"


Step 4 — Dispatch

Run the selected /portfolio:<x|y|z> command with the portfolio slug as argument. Hand off fully — do not duplicate the portfolio-manager agent's work.


Step 5 — Gate and report

After the command completes, read portfolio/<slug>/portfolio-state.md and print a status block:

Portfolio: <slug>
Cycle just run: <X|Y|Z> — <date>
Next X due: <date or "within 6 months">
Next Y due: <date or "within 30 days">
Next Z due: tomorrow
Attention items: <from cycle output, or "none">

Then ask (single AskUserQuestion): "Run another cycle now, or done for today?"


Constraints

  • Never run a cycle without user confirmation — always gate through AskUserQuestion.
  • Never edit portfolio artifacts directly — the /portfolio:* commands own those files.
  • Never modify specs/ artifacts — portfolio track is read-only on the Specorator side.
  • Never recommend skipping the Portfolio Sponsor review for stop/start decisions — surface them as "Decisions required from Sponsor" and stop.
  • If portfolio-definition.md is missing, stop and tell the user to run /portfolio:start first.

References

  • docs/portfolio-track.md — full methodology.
  • docs/sink.md — artifact locations.
  • memory/constitution.md — governing principles (especially Article VII — Human Oversight).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.