agentleFS
ridwankustantoridwankustanto/mandor/.claude/skills/pm-discover/SKILL.md

pm-discover

Skill2 starsChanged 40 days agoMITView on GitHub

Phase 1, Discover. Structured research across four fixed axes (prior art, feasibility, constraints, risk) producing research_note rows where every finding carries an implication. Use after /pm-new, when the user says "/pm-discover", "research this", "benchmark", "what are the risks", or before committing to a stack.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ask with AskUserQuestion whenever a finding forces a choice.

    line 15
  2. Distinctive:

    Use web search and Claude in Chrome for real products, not from memory.

    line 27
  3. Very specific:

    Do not create the code repo here.

    line 78

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/pm-discover: research that downstream work can rely on

Free-form research produces a different shape every project, so nothing can be compared or reused. This phase has four fixed axes. Every project gets all four, even briefly.

Every finding must have an implication. A finding with no implication is trivia and gets dropped. The implication is what changes: a story, a constraint, a risk to watch, a choice now foreclosed.

Ask with AskUserQuestion whenever a finding forces a choice. Do not pick the stack, the pattern, or the tradeoff on the user's behalf and mention it in passing.

Axis 1: prior art

Three to five products that already solve this. For each:

  • The pattern they use
  • Why it fits their context specifically
  • The tradeoff they accepted
  • Verdict: adopt, adapt, or avoid, with one line of reasoning

Use web search and Claude in Chrome for real products, not from memory. Screenshot teardowns are fair game and usually sharper than descriptions.

Axis 2: technical feasibility

What the candidate stack can and cannot do for this specific product.

  • Hard limits: rate limits, payload caps, quotas, cold starts, platform rules
  • Cost at the expected scale, and at ten times it
  • What is genuinely hard here, as opposed to merely unfamiliar
  • What already exists that you would otherwise rebuild

Axis 3: constraint scan

  • Compliance and legal: data residency, retention, consent, licensing
  • Platform rules: app store, browser extension, API terms of service
  • Auth and privacy: what trust boundaries exist, what is validated where
  • Accessibility floor: what you commit to now so it is not retrofitted later

Axis 4: risk register

The five things most likely to kill this, each with an early signal.

RiskImpact if it landsEarly signal to watchCheapest mitigation

A risk with no observable early signal is not a risk, it is a fear. Rewrite it or drop it.

Write it down

./pm add research_note axis=prior_art topic="<product>" \
  finding="<what they do>" implication="<what it changes for us>" url="<link>"
./pm add research_note axis=risk topic="<risk>" \
  finding="<why it could kill us>" implication="<the early signal to watch>"

A finding that changes scope goes straight into docs/product/overview.md, so /pm-spec builds the tree from something current. Note the research note code next to it, so the reason survives:

Constraint, from RN004: the platform forbids background sync on free tier.

Record the stack choice as an ADR the moment it is made. See /pm-change for the ADR format, or write it directly to docs/engineering/adr/0001-<slug>.md and:

./pm add adr title="<decision>" status=accepted decision="<what>" why="<what forced it>" \
  alternatives="<what was rejected and why>" doc_path=docs/engineering/adr/0001-<slug>.md

Do not create the code repo here. /pm-build creates it and links it, once there is something to put in it.

Close the gate

Present the risk register and the adopt/avoid list to the user as a form. Approve only after they respond.

./pm gate approve discover "risk register and adopt/avoid list reviewed"
./pm phase next

Download now (ZIP)

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.