agentleFS
prateekjainprateekjain/ChiefOfStaff/skills/submit-for-approval/SKILL.md

submit-for-approval

Skill4 starsChanged 8 months agoMITView on GitHub

Submit an action to the Notion Decisions DB for founder approval

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the context needed for the founder to make a decision:

    line 23
  2. Very specific:

    Create a page in the Decisions database (data source: YOUR_DECISIONS_DATASOURCE_ID):

    line 32
  3. Very specific:

    Write a note to the venture's decisions/ directory:

    line 47

≈ “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

Submit for Approval

Submit an action to the Notion Decisions DB approval queue for founder review.

Input

  • Type: One of: Deployment, Content, Outreach, Spending, Stage Change
  • Venture slug: Which venture this is for
  • Description: What action is being requested

Step 1: Prepare the Submission

Read the context needed for the founder to make a decision:

  • For Content: Include the full draft text in the Context field
  • For Outreach: Include the target, channel, and full message draft
  • For Deployment: Include what's being deployed and where
  • For Spending: Include the amount, what it's for, and ROI justification
  • For Stage Change: Include evidence that exit criteria are met

Step 2: Create Decisions DB Entry

Create a page in the Decisions database (data source: YOUR_DECISIONS_DATASOURCE_ID):

Decision: {Short title of what needs approval}
Type: {Deployment / Content / Outreach / Spending / Stage Change}
Status: Pending
Venture: {venture slug}
Submitted By: {agent name}
Urgency: {Low / Medium / High}
Date: {today}
Context: {Full details — the draft content, the action description, the evidence}

Step 3: Log the Submission

Write a note to the venture's decisions/ directory:

decisions/{date}-{slug}.md:
# Pending Approval: {title}
Submitted to Decisions DB on {date}.
Type: {type}
Waiting for founder review.

Step 4: Confirm

Report: "Submitted for approval: {title}. Check the Decisions DB in Notion to approve or reject."

The item will be executed by ChiefOfStaff during the next work cycle after the founder marks it "Approved".

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.