claude

j-flow

Gate-based Spec-Driven Development workflow for MongoDB + NestJS + React + Flutter projects.

1 on GitHubby jotafierrov2.5.1MITupdated 2 months ago
/

Plugin j-flow from marketplace j-flow-marketplace in jotafierro/j-flow. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (17)

  • j-flow-release-repo

    Release checklist for the j-flow plugin repo itself (migration guide, version bump, changelog, tag, GitHub release). Use when cutting a new j-flow version — not for /j-flow-release, which is for target projects that consume the plugin.

  • j-flow-build

    Implement tasks from the approved plan. Dispatches domain agents by layer, sequentially except ui+mobile which run in parallel when both have tasks. --fix mode resolves QA or review findings. Usage: /j-flow-build [--fix]

  • j-flow-check

    Read-only inspector. Default shows feature status and gate progress; --repo runs repo health diagnostics (drift, missing artifacts); --consistency runs AC↔task↔test cross-consistency for the active feature. Usage: /j-flow-check [--all | --repo | --consistency] [--verbose]

  • j-flow-eject

    Copy a j-flow template, reference, agent definition, or agent memory file from the plugin into the target repo under `.specs/.overrides/` so it can be customized without forking. Usage: /j-flow-eject [asset-path]

  • j-flow-finish

    Generate feature README, update CHANGELOG [Unreleased], consolidate agent memory patterns, and integrate the feature branch (PR in team mode, local merge in solo). Usage: /j-flow-finish

  • j-flow-plan

    Generate task plan (tasks.json) and review guide (review-guide.md) from approved specs. Validates AC coverage before saving. Usage: /j-flow-plan

  • j-flow-project

    Define or update the project for a j-flow repo (MongoDB + NestJS + React + Flutter). Init mode generates PRODUCT.md, DESIGN.md, CHANGELOG.md, .specs/README.md (phased feature backlog), and agent memory, then auto-invokes /j-flow-scaffold. Update mode syncs backlog statuses from meta.md files, allows

  • j-flow-qa

    Run full QA gate across 7 stages: lint, unit tests, NestJS E2E, Flutter integration, Playwright E2E, visual smoke check, manual checklist — layer-aware, skips stages for untouched layers. Blocks /j-flow-review if red. Usage: /j-flow-qa

  • j-flow-recommend

    Recommends plugins, skills, and tools that enhance the j-flow workflow. Invoked automatically at the end of /j-flow-scaffold. Can also be run standalone any time. Usage: /j-flow-recommend

  • j-flow-release

    Cut a release — semver bump, CHANGELOG, tag, GitHub Release. Usage: /j-flow-release [major|minor|patch]

  • j-flow-reopen

    Reopen a feature to a prior gate. Clears gate-context.md from the chosen gate forward. Does NOT revert commits. Usage: /j-flow-reopen [slug]

  • j-flow-review

    Audit code quality against approved technical specs. Only reachable if QA gate is green. Produces review-findings.md. Usage: /j-flow-review

  • j-flow-scaffold

    Scaffolds the monorepo using official CLIs (nest new, pnpm create vite, flutter create, npx storybook init) at pinned, known-good versions. Generates health endpoint, README, CHANGELOG entry, and review-guide for manual verification. Manual approval gate before marking 01-infra-base as done. Auto-tr

  • j-flow-shared

    Bundle of shared templates and references for j-flow skills. This skill is not user-invocable — it exposes assets at known paths. Skills and agents read files in `templates/` and `references/` directly via `${CLAUDE_PLUGIN_ROOT}`.

  • j-flow-spec

    Generate functional spec (default) via dialogue, or technical spec (technical argument) via j-flow-architect agent, or explore scope without committing (--explore). Both spec modes produce approval gates. Usage: /j-flow-spec [technical|--explore]

  • j-flow-start

    Initialize a new feature. Creates git branch, .specs/{slug}/ directory, meta.md, and empty gate-context.md. Loads agent memory context. --quick marks the feature fast-track (collapses redundant confirmations in later gates). Usage: /j-flow-start {slug} [--quick]

  • j-flow-update

    Update specs or task plan mid-feature due to changed requirements. Marks downstream gates as stale. Usage: /j-flow-update

Subagents (8)

  • j-flow-architect

    Generates technical specs for MongoDB + NestJS + React + Flutter projects. Domain expert across the full stack. Reviews functional specs, proposes technical structure, validates cross-layer coherence. Use for /j-flow-spec technical.

  • j-flow-backend

    Implements NestJS + MongoDB code. Writes Mongoose schemas, DTOs, services, controllers, guards, pipes, and NestJS E2E specs (supertest). TypeScript-first. Use for data, service, and api build layers.

  • j-flow-cli

    Implements TypeScript command-line tools with commander. Subcommands, argument/flag parsing, exit-code + stdout/stderr contract, picocolors output, config files, tsup bundling to a self-contained bin. Use for the cli build layer.

  • j-flow-devops

    Configures infrastructure: Docker Compose, GitHub Actions CI/CD, Railway (backend), Vercel (frontend), environment variables. Does NOT write app code. Use for infra build layer.

  • j-flow-frontend

    Implements React + TypeScript UI. Components, hooks, pages, Storybook stories. Knows React Query (server state), Zustand (client state), react-hook-form, zod, and either Tailwind CSS or plain CSS (per project's Styling choice). Use for ui build layer.

  • j-flow-mobile

    Implements Flutter + Dart code. Widgets, screens, state management (Riverpod), GoRouter navigation, Widgetbook catalog, integration_test specs. Use for mobile build layer.

  • j-flow-quality

    Runs the full test suite and validates QA gate. Executes jest/vitest, NestJS E2E (supertest), flutter test, integration_test, Playwright, and visual smoke. Generates qa-report.md and determines gate status.

  • j-flow-reviewer

    Audits code quality against approved technical specs. Detects speculative behavior, premature abstractions, pattern violations, security gaps, and performance issues. Produces review-findings.md. Use for /j-flow-review.

View source on GitHub

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development

9 skills · 1 command · 8 agents

wshobson/agents 42,461

beads

claudecodex

AI-supervised issue tracker for coding workflows

1 skill · 1 agent · hooks

gastownhall/beads 28,698

MiniMax AI skills library for frontend, fullstack, Android, iOS, shader, GIF sticker, document, presentation, spreadsheet, and multimodal media workflows

18 skills

MiniMax-AI/skills 13,828

worktrunk

claudecodex

Worktrunk is a CLI for Git worktree management, designed for parallel AI agent workflows. This plugin provides configuration guidance (LLM commit messages, project hooks, worktree paths), automatic activity tracking (🤖/💬 indicators in `wt list` showing active Claude sessions), and a `/wt-diff` pane showing each worktree's changes.

2 skills · hooks

max-sixty/worktrunk 12,481

gsd-core

claude

GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.

72 skills · 72 commands · 64 agents · hooks

open-gsd/gsd-core 11,494

Maintain j-flow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted