friday-3-create-todos
Skill0 starsChanged 5 months agoMITView on GitHub
Step 3 of the Friday workflow. Read all definitions marked with FRIDAY-DEFINITION comments across the codebase and generate implementation todos — one set per definition. Use only when explicitly told to execute Step 3 of the Friday workflow.
In this repository7 other files it gives its agents.
- friday-1-create-data-structuresSkill
- friday-2-create-definitionsSkill
- friday-4-implement-todosSkill
- friday-5-cleanupSkill
- html-flow-explainSkill
- html-planSkill
- html-pr-reviewSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 15
Do not use this skill for standalone TODO generation outside the Friday workflow.
- Very specific: line 21
Search the entire codebase for FRIDAY-DEFINITION comments:
- Distinctive: line 55
If a TODO references a data structure from Step 1, use the exact type/field names
- Very specific: line 59
If definition A depends on definition B being implemented first, note it: TODO 3: Call parseInviteCode() from AuthService (depends on …
- Very specific: line 65
If the function already has a body with a placeholder (e.g., return null), place the todos before it
- Distinctive: line 70
Before (definition from Step 2):
- Distinctive: line 78
After (with todos inserted):
≈ “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.
Files
Friday Step 3: Create Implementation TODOs
This is the third step in the Friday workflow. After function/component definitions are created (Step 2), scan the codebase for all FRIDAY-DEFINITION comments and generate step-by-step implementation todos for each one.
When to use
- User explicitly says "Friday step 3" or "friday-3"
- Following a Friday workflow where Step 2 is already complete
Do not use this skill for standalone TODO generation outside the Friday workflow.
Workflow
1. Find all definitions
Search the entire codebase for FRIDAY-DEFINITION comments:
rg "FRIDAY-DEFINITION" --include "*.{ts,tsx,js,jsx,go,py,rs,java,kt}" -A 3For each match, record:
- The file path and line number
- The description from the FRIDAY-DEFINITION comment
- The function/component signature
2. Generate todos for each definition
For each definition found, generate a set of implementation todos. Insert the todos inside the definition body (after the opening brace or within the function body, before any return/placeholder).
Each todo block must use this exact format:
/*
* FRIDAY-WORKFLOW
* FRIDAY-TODO
* FRIDAY-TODO-STATUS: PENDING
* TODO 1: {actionable step — what to do first}
* TODO 2: {actionable step — what to do second}
* TODO 3: ...
*/3. Rules for writing good todos
- Each TODO must be actionable — start with a verb (Fetch, Validate, Parse, Call, Render, etc.)
- Each TODO must be specific — mention exact parameters, fields, or conditions where relevant
- Order TODOs in logical implementation order (first thing first)
- 2-8 TODOs per definition — too few means the steps are too coarse, too many means they're too granular
- If a TODO references a data structure from Step 1, use the exact type/field names
4. Handle dependencies
- If definition A depends on definition B being implemented first, note it:
TODO 3: Call parseInviteCode() from AuthService (depends on AuthService.parseInviteCode) - Cross-file dependencies should be explicit
5. Placement
- Insert the todo block right after the opening brace of the function/component body, before any existing code
- If the function already has a body with a placeholder (e.g.,
return null), place the todos before it - For React components, place inside the component function body
Example
Before (definition from Step 2):
export async function createTeam(
params: CreateTeamParams,
options?: { generateInvite?: boolean }
): Promise<Team>;After (with todos inserted):
export async function createTeam(
params: CreateTeamParams,
options?: { generateInvite?: boolean }
): Promise<Team> {
/*
* FRIDAY-WORKFLOW
* FRIDAY-TODO
* FRIDAY-TODO-STATUS: PENDING
* TODO 1: Validate params.name is non-empty and within length limits
* TODO 2: Check slug uniqueness in database
* TODO 3: Hash the team name for slug generation
* TODO 4: Insert Team record into database
* TODO 5: If options.generateInvite, call generateInviteCode(team.id)
* TODO 6: Return the created Team
*/
}After completing
Report how many definitions were found and how many todo blocks were created. Do not move to Step 4 unless instructed.
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
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.

