pdev-jay/plugins

asciify — validated architecture, workflow, sequence, data-flow and lifecycle diagrams as Unicode box-drawing text, written into the project's docs/ folder as Markdown. Geometry is checked on an integer grid, source citations and drill-down links are verified against the working tree, and the JSON IR is embedded in the document for lossless round-trip editing.

Collective-intelligence-driven development for Claude Code — each stage (explore/plan/build/review) takes a different orchestration shape based on oracle availability: explore=divergent generation+judge, plan=lens friction, build=generate-verify-repair, review=hard-oracle gate with advisory lenses.

Flow-driven development for Claude Code — plan around the FLOW of what you change instead of guessing a single 'root'. Skill-centric: plan → build → review → done.

jay-flow — lightweight plan→build→review→done loop for Claude Code. Conversational planning over a fixed check-axis list (no lens fan-out; the user is the friction source), implementation fanned out to a sonnet builder with oracle-green gates, judgment kept on the main (higher) model.

Floor-first agentic coding workflow for Claude Code — machine-enforced gates (intent-before-code, verify-before-done) over an ephemeral task file. Context derived from code, not authored.

Skills, agents, and hooks for Vault-Driven Development — a per-project descriptive Source-of-Truth pattern for Claude Code workflows.