agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/working-backwards/SKILL.md

working-backwards

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to create an Amazon-style Working Backwards artifact or serious written decision artifact before discussion. Use for PR/FAQ, PRFAQ, press release FAQ, internal press release, six-page narrative memo, narrative decision memo, one-way door versus two-way door decision framing, memo-read meeting protocol, decision log, customer-backward product or service design, replacing slides with a memo, or a major product, strategy, operating model, pricing, governance, board, or executive approval decision that needs written reasoning before debate. Use when the user says working backwards, Amazon method, write the decision memo, draft the PR/FAQ, start from the customer outcome, or make this board-grade before discussion. Do not use for routine status updates, simple PRDs, feature specs, lightweight SOPs, casual brainstorming, small reversible approvals, generic strategy notes, or generic mental-model explanations. If the primary task is a PRD or feature requirements document, use create-prd. If the primary task is product direction or strategy canvas work without a decision memo, use product-strategy. If the primary task is failure-first risk testing, use pre-mortem. If the primary task is delivery sequencing, roadmap, dependency tree, or WBS, use wbs-artifact-planner. If the primary task is a controlled SOP, policy, workflow, or governance artifact, use ssot-drafter.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. 0 are common, 18 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 18

    Distinctive

    This author's own choices. Worth a look.

  • 2

    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 measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “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