agentleFS
anirudhaxeanirudhaxe/friday-skills/skills/friday-4-implement-todos/SKILL.md

friday-4-implement-todos

Skill0 starsChanged 5 months agoMITView on GitHub

Step 4 of the Friday workflow. Implement all TODOs marked with 'FRIDAY-TODO-STATUS: PENDING' across the codebase. Preserve existing code that has status DONE or no status. Implements function bodies, component logic, and business rules based on the todo steps. Use only when explicitly told to execute Step 4 of the Friday workflow.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not use this skill for standalone implementation outside the Friday workflow.

    line 15
  2. Very specific:

    Only implement code blocks with FRIDAY-TODO-STATUS: PENDING.

    line 23
  3. Distinctive:

    Read the full function signature and surrounding code

    line 41
  4. Distinctive:

    Read the data structures from Step 1 (types, schemas)

    line 42
  5. Very specific:

    Remove the FRIDAY-TODO and FRIDAY-TODO-STATUS: PENDING lines as part of the implementation — they are replaced by real code

    line 45
  6. Distinctive:

    After replacing the FRIDAY-TODO block with code:

    line 58
  7. Very specific:

    Update FRIDAY-TODO-STATUS: PENDING to FRIDAY-TODO-STATUS: DONE — wait, no.

    line 60
  8. Distinctive:

    When implementing a function that calls another Friday-defined function, import and call it — don't reimplement the logic

    line 65
  9. Distinctive:

    If you encounter a PENDING todo that depends on another function still marked PENDING, check if that other function is in the same file or …

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Friday Step 4: Implement TODOs

This is the fourth step in the Friday workflow. After TODOs are generated (Step 3), implement all pending ones by replacing each FRIDAY-TODO block with actual code.

When to use

  • User explicitly says "Friday step 4" or "friday-4"
  • Following a Friday workflow where Step 3 is already complete

Do not use this skill for standalone implementation outside the Friday workflow.

Important constraint

NEVER modify or remove code that has:

  • FRIDAY-TODO-STATUS: DONE — already implemented, leave it alone
  • No FRIDAY-TODO-STATUS line at all — not part of this workflow, leave it alone

Only implement code blocks with FRIDAY-TODO-STATUS: PENDING.

Workflow

1. Find all pending todos

Search the codebase:

rg "FRIDAY-TODO-STATUS: PENDING" --include "*.{ts,tsx,js,jsx,go,py,rs,java,kt}" -B 10

For each, read the surrounding code to understand the full function context.

2. Implement each todo block

For each FRIDAY-TODO-STATUS: PENDING block:

  1. Read the full function signature and surrounding code
  2. Read the data structures from Step 1 (types, schemas)
  3. Implement the function body following the TODOs in order
  4. Replace the entire FRIDAY-TODO block (the multiline comment) with the actual implementation code
  5. Remove the FRIDAY-TODO and FRIDAY-TODO-STATUS: PENDING lines as part of the implementation — they are replaced by real code

3. Implementation rules

  • Follow the project's conventions — use the same patterns, error handling style, logging approach, and coding idioms as surrounding code
  • Use existing utilities — check for helper functions, libraries, and services already in the codebase before writing new ones
  • Handle errors — add error handling appropriate to the function (try/catch, Result type, error boundaries, etc.)
  • Write complete code — not pseudocode or placeholders
  • Respect types — all code must compile with the existing type system
  • Keep functions focused — if a TODO says "Validate input and return errors", don't also do the database call in the same block

4. After implementation

After replacing the FRIDAY-TODO block with code:

  • Update FRIDAY-TODO-STATUS: PENDING to FRIDAY-TODO-STATUS: DONE — wait, no. Per the workflow, the entire FRIDAY-TODO comment block is removed and replaced with real code. The TODOs served their purpose as a plan; they don't stay as comments.
  • Actually, re-read: the TODOs are a multiline comment inside the function body. When implementing, replace that comment with actual code. Do not leave the TODO comment in place with DONE status. Remove it entirely.

5. Cross-function integration

  • When implementing a function that calls another Friday-defined function, import and call it — don't reimplement the logic
  • If you encounter a PENDING todo that depends on another function still marked PENDING, check if that other function is in the same file or module and implement it in the same pass
  • For cross-module dependencies, implement in dependency order

Common pitfalls

  • Don't leave FRIDAY-TODO comments in implemented code — they get replaced, not updated
  • Don't modify existing (non-PENDING) code — only touch PENDING todo blocks
  • Don't add new FRIDAY-TODO comments — this step removes them, it doesn't create them
  • Don't skip error handling — every function that can fail should handle errors appropriately

After completing

List each file modified and summarize what was implemented. Do not move to Step 5 unless instructed.

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.