agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/wbs-artifact-planner/SKILL.md

wbs-artifact-planner

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to break down, decompose, sequence, structure, plan, roadmap, or turn a large initiative into a WBS, work breakdown, workstream plan, delivery plan, implementation plan, artifact plan, issue tree, project tree, dependency map, execution roadmap, or node-based plan. Use for strategies, development efforts, documentation programs, governance buildouts, product initiatives, audits, implementations, research programs, artifact creation programs, and multi-deliverable work where nodes, dependencies, deliverables, validation methods, owners, statuses, acceptance gates, or execution order matter. Use when the user asks for GitHub issues, Linear issue structure, task contracts, delivery sequencing, work packages, milestones, acceptance gates, or a traceable plan that can be executed and reviewed. Do not use for casual todo lists, single-document drafting, ordinary brainstorming, generic strategy notes, or simple next-step advice. If the primary task is a PRD or feature requirements document, use create-prd. If the primary task is a serious written decision memo or PR/FAQ, use working-backwards. If the primary task is failure-first risk testing, use pre-mortem. If the primary task is a controlled SOP, policy, workflow, or governance artifact, use ssot-drafter. If the primary task is designing the surrounding artifact system, folder structure, metadata, lifecycle, or source-of-truth model, use artifact-system-designer. If the primary task is validation checklist, defect log, evidence requirements, or pass/fail readiness, use artifact-validation-workflow.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.

Check your setup, free