What problem does it solve? Job sets drafted without implementation contact produce product scopes nobody can build, and the gap surfaces only after development starts. This Skill performs a planning-time reality check on a drafted job set before scope is committed. ## Core Features & Use Cases - Codebase and service sweep: Inspects the target repo for existing integrations, stack bindings, auth models, and seams, then checks every external service the jobs imply for access, auth shape, cost, and rate ceilings. - Decision-filtered findings: Keeps only findings that change a scope call, job feasibility, sequencing, or buy-vs-build, each rated cheap/moderate/expensive/unknown with a confidence level and a resolving evidence pointer. - Ledger-routed output: Returns findings through the Know/Don't Know ledger under a three-way answer rule — verifiable from the repo, covered by a Declared default, or routed as a question — with substance landing in research-plan.md and jobs carrying citations only. - Use Case: A discovery phase drafts five jobs implying a payments provider and per-user OAuth. The Skill verifies the provider's API access terms, flags the OAuth consent flow as a first-run product fact, rates one job expensive with moderate confidence, and routes a blocking partnership question to research. ## Quick Start Run the dev-research skill against this target repository and the drafted job set to produce confidence-rated feasibility findings routed through the ledger.
