clean-style
claudeApply a strict anti-AI-slop writing checklist to external-facing prose. The shared baseline other skills in this repo defer to.
1 skill
Six skills covering an initiative's full lifecycle: Working Backwards PR/FAQ, use-case discovery, UML use cases, test cases, trackable requirements, and persona-driven architecture review with an opt-in debate.
Plugin product-management from marketplace claude-skills in ToddE/claude-skills. Commands read from the repo's manifest — 1 month ago.
architect-reviewProduce a structured architectural recommendation for an initiative, from the perspective of a specific Sr. Architect persona, using whatever pipeline artifacts exist: PR/FAQ, use case(s), functional requirements, or just a description if that's all there is. Use this skill when the user asks for an
build-planTurn product planning artifacts (use cases, functional requirements, test cases, an architecture review, a PR/FAQ) into an implementation plan that an unattended build can follow: ordered milestones with gates, a task table with a model and effort level for each task, project rules and stop conditio
use-case-discoveryInterview the user about a feature or initiative at a high level and decompose it into a candidate list of use cases (name, one-line summary, rough actors, rough trigger) before any of them get fully written up. Use this skill when the user has a loose idea, a set of high-level requirements, or a fe
use-case-requirementsDerive trackable functional requirements, either from a completed use case (written with the use-case-uml skill) or, when no use case exists yet, from a short interview modeled on working-backwards-prfaq's intake. Requirements trace to something the user said or the use case states, never invented.
use-case-test-casesGenerate test cases directly from a UML-style use case (written with the use-case-uml skill or in that same format): one test case per Basic Path, Alternate Path, and Exception Path, with expected results taken from the use case's Post-Condition(s). Use this skill any time the user asks to "write te
use-case-umlWrite UML-style integration use cases (actors, basic path, alternate paths, exception paths, post-conditions) in a fixed, repeatable structure. Use this skill any time the user asks to write a "use case," "integration use case," "user flow," or wants to document a system/actor interaction with a bas
working-backwards-prfaqGenerate Amazon-style Working Backwards PR/FAQ documents for any kind of announcement: a new product, a partnership, a nonprofit initiative, a political campaign, a community program, or anything else defined by starting from the audience's experience and working backwards. Use this skill any time t
Apply a strict anti-AI-slop writing checklist to external-facing prose. The shared baseline other skills in this repo defer to.
1 skill
Standalone use case skill: scope a feature into candidate use cases, then write each one in full (actors, basic/alternate/exception paths, post-conditions) in one fixed format. No other skills required.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.