agentsclimarketplace

Foundation

Skill Zhen-Bo/request-devflow-plan/skills/foundation

Claude Code plugin: tech-lead interview -> multi-file execution plan -> sprint-by-sprint execution -> zero-trust audit -> handoff. Guarded against both lazy shortcuts and over-engineering.

Install
npx -y skills add Zhen-Bo/request-devflow-plan --skill foundation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate the DevFlow foundation for a repo without committing to a full plan — as-is docs/SPEC skeleton (architecture, contracts, glossary, decision log), the core Mermaid diagram set, a one-command verification gate runner, a codebase guide, and the diagram-led / SPEC-assisted workflow conventions. Use when the user wants just the documentation and diagram foundation, a SPEC skeleton, or architecture docs — no sprints, no execution plan. Triggers: foundation, bootstrap docs, SPEC skeleton, architecture diagrams, 基座, 地基, 文檔基座.

SKILL.md

3.8 KB, as published. Nobody here has run it

request-devflow-plan:foundation

Build the DevFlow foundation (diagram-led, SPEC-assisted) as a standalone product — everything a plan's Sprint 0 would build, without a plan folder, sprints, or iron rules. Write all generated documents in the user's conversation language. Documentation is strictly as-is: it records what exists, never aspirations.

Flow

Step 1 — Recon

Read the repo: CLAUDE.md, README.md, package manifests, source layout, tests, CI, existing docs/SPEC/ and docs/diagrams/. Inventory what already exists — existing pieces are never rebuilt, only gap-filled.

Step 2 — Confirm scope

One AskUserQuestion, only when recon leaves it genuinely ambiguous: which diagrams apply (per the selection table in ../plan/references/devflow-distilled.md — UI flow for frontends, state machines where stateful entities exist) and where the docs live (default docs/SPEC/ and docs/diagrams/).

Step 3 — Generate (gap-fill only)

  1. SPEC skeleton: docs/SPEC/ARCHITECTURE.md (module boundaries + allowed dependency directions), docs/SPEC/specs/API_CONTRACT.md (sole wire-contract authority; no API → a domain behavior contract instead), GLOSSARY.md, DECISIONS_AND_CHANGELOG.md.
  2. Core as-is diagrams: the required set from the selection table (C4 container, package/dependency, ER, one sequence per core write path, state machines for stateful entities, deployment; UI flow for frontends). Mermaid in Markdown, zero toolchain; each file pinned to: purpose / diagram / contracts the picture can't carry → SPEC link / last-calibrated commit.
  3. Verification gates: a one-command runner wrapping the repo's existing type check / lint / test tooling, in the repo's native shell (exit codes never read through a pipe; skipped ≠ green). Missing harness → record it as a gap with a recommendation; do not build one here.
  4. Codebase guide: a module map + conventions document (CODEBASE_GUIDE.md, or the repo's existing equivalent extended).
  5. Workflow conventions: docs/SPEC/WORKFLOW.md — the five SPEC rules (SPEC before code; report mismatches, never self-adjudicate; never edit SPEC to fit code; never delete a SPEC file; behavior changes sync SPEC in the same commit) plus the diagram-first loop and anti-drift habits, stated as standing repo conventions.

Step 4 — Self-check and deliver

  • Every structural claim in a generated document (module, dependency direction, table, endpoint, state) carries file:line evidence gathered during recon — a claim without evidence may not be written. Run every gate command once and show the output.
  • Deliver the inventory: created / extended / already existed / gaps noted.
  • End with the Next steps block — full copy-paste command (never shorthand), preceded by the advisory "Run /clear (or open a new session) first": /request-devflow-plan:plan — plan real work; its recon finds this foundation and skips Sprint 0 basework (noted gaps, e.g. a missing test harness, become Sprint 0 items there) Docs were all you wanted → done; keep the diagrams calibrated per WORKFLOW.md.

Never

  • Document aspirations as reality (as-is only)
  • Rebuild anything that already exists
  • Introduce new tooling — the gate runner wraps what the repo already has

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.