agentleFS
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/portfolio-rebalancing/manual/skills/aibast_execution-plan_06/SKILL.md

execution-plan

Skill8 starsChanged 3 months agoMITView on GitHub

Use for human-controlled implementation checklist questions in the Portfolio Rebalancing Agent synthetic pilot.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the supplied cadence. Proposed post-trade verification means matching source targets.

    line 25
  2. Distinctive:

    Every checklist item is a proposed human step, not a completed approval, prepared notification, record update or trade.

    line 27

≈ “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
<!-- bic:source=blank -->

Human-controlled implementation checklist

Retrieve the paired synthetic records and controls. Organize the supplied candidate and review sequence without authorizing or performing an action. Use the requested fictional record or the configured PORT-5001 default; never substitute another record for an unknown ID.

Response shape

Return only:

  1. Portfolio identity, source citation, supplied rebalance cadence and the candidate count verified against the actual entries.
  2. The source reduction and increase candidates, with their exact amounts and candidate-only labels. For PORT-5001 these are VTI reduction $622,500, VB increase $372,500 and VEA increase $373,750. Preserve the source totals if totals are shown.
  3. This pending cash/settlement review: Confirm available cash and settlement timing in the approved trading system.
  4. Required human review by the licensed financial advisor, portfolio manager, qualified tax professional, compliance reviewer, client and authorized trading supervisor as applicable. Required approvals remain pending before any order.
  5. Proposed verification that allocations match their source targets, followed by proposed portfolio-record updates, client notification and compliance documentation. These steps have not occurred.
  6. The exact no-order statement and footer below.

Quantity and action boundaries

Cash review must consider available cash, settlement and the candidate cash flows together. The $622,500 reduction is smaller than the $746,250 increases; reduction proceeds alone are not the source's funding condition. Do not invent a proceeds-only approval gate, assert an external funding shortfall, or treat a recorded cash holding as verified available or settled cash.

Use the supplied cadence. Proposed post-trade verification means matching source targets; no post-trade tolerance is supplied. Do not turn detection thresholds into trading permission, infer that other holdings need no action, or append a new tax calculation, strategy essay or system recommendation.

Every checklist item is a proposed human step, not a completed approval, prepared notification, record update or trade. This pilot cannot access the approved production systems named in the source.

State exactly: No order has been created, routed, or executed.

End every substantive answer with exactly:

Synthetic portfolio evidence only; not investment, tax, legal, retirement, or financial advice. No order or transaction occurred. Licensed human review required.

Locked example

Persona: Trading Supervisor

Prompt: Prepare the controlled implementation checklist and make clear whether any order was sent.

Expected synthetic evidence: VTI, No order.

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.