list-tasks
Skill2 starsChanged 55 days agoMITView on GitHub
Browse available tasks (user story or bug) from the project's docs/ folder. Lists them for selection, then hands off to analyze-task for deeper validation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ryanlewis/claude-crontheir own version, first seen Feb 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ryanlewis/claude-cron★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- analyze-taskSkill
- implement-taskSkill
- prepare-for-wishesSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When this skill is loaded, you help the developer browse available tasks (user stories or bugs) stored in <project_root>/docs/ folder.
- Very specific: line 16
Read ../globals/INDEX.md and follow its instructions to load all globals.
- Very specific: line 22
If the developer asks to validate or analyze a specific task (e.g., "validate this user story", "analyze bug"), do not proceed with listing.
- Distinctive: line 24
If they want to list, browse, or show tasks, proceed.
- Distinctive: line 28
If the developer already stated the type (e.g., "list available bugs"), infer it directly — do not ask.
- Distinctive: line 41
If there are more than 5 items, show the first 5 and ask: *"Show the next 5?"* Repeat until all are shown.
- Distinctive: line 42
If there are more than 15 items, after paginating, suggest: *"There are many tasks — consider using a more specific search (e.g., grep for …
- Very specific: line 46
After listing, ask: Which task would you like to analyze?
≈ “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.
Files
List Tasks Skill
When this skill is loaded, you help the developer browse available tasks (user stories or bugs) stored in <project_root>/docs/ folder.
Command syntax: jenie commands are written here as
/jenie <name>. In OpenCode use them as-is (e.g.,/jenie analyze-task); in Claude Code they are namespaced with a colon (e.g.,/jenie:analyze-task); in Copilot use the skill name directly (e.g.,/analyze-task). Always show the developer the syntax that matches the current environment.
Pre-condition
1. Load Global Guidelines
Read ../globals/INDEX.md and follow its instructions to load all globals. Cache them for the session. This must complete before any workflow step.
Workflow
1. Determine intent
If the developer asks to validate or analyze a specific task (e.g., "validate this user story", "analyze bug"), do not proceed with listing. Instead, tell them to use /jenie analyze-task for that and stop.
If they want to list, browse, or show tasks, proceed.
2. Determine task type
If the developer already stated the type (e.g., "list available bugs"), infer it directly — do not ask.
Otherwise, ask: Is this a user story or a bug?
3. Locate tasks folder
Look in <project_root>/docs/{type}s/ (e.g. <project_root>/docs/user-stories/ or <project_root>/docs/bugs/). If the folder doesn't exist or is empty, ask the developer for an alternative location to browse (e.g., another directory or a specific file path). If they provide one, update the search path and continue. If they don't, inform them no tasks can be listed and stop.
4. List available tasks
Read the files found in the folder (use glob to list them, then read each). For each file, extract a short description — read the first 5 lines or until the first blank line to get the title or narrative (e.g., the "As a… I want…" line). Present them as a numbered list with the description.
Pagination:
- If there are more than 5 items, show the first 5 and ask: "Show the next 5?" Repeat until all are shown.
- If there are more than 15 items, after paginating, suggest: "There are many tasks — consider using a more specific search (e.g., grep for a keyword) inside the folder to narrow down."
5. Next steps
After listing, ask: Which task would you like to analyze? When they pick one, suggest using /jenie analyze-task to validate it with INVEST + 3C.
Throughout the workflow, follow the loaded global guidelines.
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.