andrewluxem/3ps-framework

Turns raw notes into a Weekly 3Ps Update, one team update under three headings, Progress, Plans, and Problems. Use this skill when the update is a person's or a team's week in Progress, Plans, and Problems, including when the request never says 3Ps. Trigger on phrasings like write up my week, what I got done and what is next, my weekly team update, turn these notes into my update. It answers to the format by name too, 3Ps, 3P update, Progress Plans Problems, or the 3ps-framework skill, and to a request to revise an existing update into that shape. Input is bullets, a rough dump from the week, or a previous update. Output is one update under 200 words, with progress stated as outcomes, every plan dated and owned, every problem carrying a specific ask, and anything the notes did not supply left as a visible placeholder rather than a guess. Use weekly-status-updates instead when the update is one project's position against its plan and its date.

Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.

Source:

github.com/andrewluxem/3ps-framework

Provenance:

Found by crawling (provenance, not a security rating)

We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.