foundry-research

Plugin foundry-research from marketplace foundry in fedcal/foundry. Commands read from the repo's manifest — 1 month ago.

Skills (5)

• api-reference

  Generate reference documentation from the source of truth — OpenAPI, protobuf, JSON Schema, Javadoc, TypeDoc, docstrings or CLI help — and keep it verified against the code with CI gates. Use when reference material is hand-written, drifting, incomplete, or when a public API has no machine-readable

• docs-site

  Bootstrap or audit a documentation site for an open source project — Diátaxis structure, navigation, search, versioning, translation, ownership and the CI pipeline that fails when docs rot. Use when a project has scattered markdown, a wiki nobody trusts, or a docs site with no owner and no build gat

• evaluate-technology

  Compare candidate technologies end to end and emit an adr.v1 recommendation. Use when choosing a framework, database, queue, auth provider, observability vendor or any dependency that will be expensive to remove. Fixes weights before scoring, measures maintenance signals instead of citing popularity

• research-domain

  Run a disciplined multi-source sweep of an unfamiliar business domain before design starts. Use when the team cannot name the users, the workflow being replaced, or the domain vocabulary. Fixes the questions first, searches several distinct angles, records every claim with a source tier and two date

• write-readme

  Write or repair a README that actually works — one-sentence what, who it is for, honest non-goals, install, a 60-second first success, then links out. Use when a project has no README, a README that is a wall of badges and marketing, or one where a newcomer cannot get a working result. Includes an a

Subagents (5)

• docs-architect

  Use when documentation must become a system rather than a folder of markdown — designing the information architecture, mapping audiences to Diátaxis quadrants, choosing and wiring the docs-as-code toolchain, defining versioning and translation strategy, and assigning a named owner and review cadence

• domain-researcher

  Use before any code, schema or UI exists, when the team does not yet speak the language of the business it is automating. Establishes who the users actually are, the manual or incumbent workflow being replaced, the domain vocabulary with its real definitions, the regulatory frame, what practitioners

• evidence-verifier

  Use when a single claim is about to become load-bearing — a benchmark number in an ADR, a regulatory obligation, a compatibility guarantee, a vendor SLA, a "framework X supports Y" assertion, or any statistic quoted into a decision. Attempts to refute the claim rather than confirm it, chases every c

• tech-scout

  Use when a technology must be chosen and living with the wrong choice would be expensive — a framework, database, queue, auth provider, observability vendor, or a dependency that will end up in every module. Scores candidates against maintenance signals, licence compatibility, operational burden and

• technical-writer

  Use to write or revise a documentation page to a stated house style — task-oriented titles, one idea per paragraph, examples that actually run, no marketing language, terminology drawn from the project glossary. Works on a page whose Diátaxis quadrant and audience are already assigned. Do not use to

Similar plugins