manhnc-dev/jstack
Requirement and design in, reviewable implementation plan, sub-500-line PR plan, and verified PRs out. Agent teams with evidence.
Use when turning a requirement and a design into a reviewable implementation plan with class and method level sequence diagrams, a change table, and a three-tier test plan (unit, component, blackbox) that covers every end-to-end scenario.
Run the whole stack from the pr-plan, implement then verify each PR in dependency order, stop at the first FAIL. For an unattended run after the human gates.
Which jstack command fits what you are trying to do, and where the artifacts land.
Implement one PR from the pr-plan on its own stacked branch with a fresh implementer agent, test first, small commits. Measures size. Then runs $jstack-verify unless --no-verify.
Interview this repo and write docs/jstack/repo-profile.md (build, test, lint, live, conventions, baseline). Run once per repo and again when tooling changes.
Turn a requirement (and optional design) into docs/jstack/<slug>/implementation-plan.md with class and method level sequence diagrams, checked and reviewed. Stops at the human gate. Does not implement.
Split an implementation plan into docs/jstack/<slug>/pr-plan.md, a stack of PRs each under 500 changed lines with tests, checked and reviewed. Stops at the human gate. Does not implement.
The eight working principles every jstack agent applies. Read before planning, splitting, implementing, or verifying with jstack, and whenever a decision about diff size, evidence, or sequencing comes up.
Independently verify one implemented PR with three fresh workers. The gates lane runs base and head suites, measures size, checks plan conformance, captures evidence, writes report.md, rerun.sh and artifacts under docs/jstack/<slug>/verification/<PR-n>/; two audit lanes read the diff against the plan; the coordinator folds their findings into the report and the bundle checker gates the result.
Verify the whole feature end to end at the top of a jstack stack. One fresh gates worker runs the full suite, every component test and every blackbox test against the booted app with stubs, and writes docs/jstack/<slug>/verification/stack/report.md with one row per plan scenario. PASS, PARTIAL when blackbox could not run, or FAIL.
Split a checked implementation plan into a stack of dependent PRs under 500 changed lines each, with a Conventional Commits title, tests, a verify command, and a rollback for every PR, then prove the split with the checker.
Interview a repository and write docs/jstack/repo-profile.md, the single source of build, test, test tier, lint, live, blackbox boot, and convention facts every other jstack skill reads. Use for $jstack-init or when the profile is missing or stale.
Rules for drawing Mermaid sequence diagrams at class and method level for jstack implementation plans and reviews. Use when writing or reviewing an SD-n block.
The three test tiers every jstack plan carries (unit, component, blackbox), how end-to-end scenarios are derived from a requirement and its diagrams, and how each tier runs on Java/Spring and NestJS repos. Read when writing or reviewing a plan's Test plan section, when splitting tests across PRs, or when implementing or verifying a PR's tests.
Produce the per-PR verification bundle (report.md, rerun.sh, artifacts/) under docs/jstack/<slug>/verification/<pr-id>/ with a baseline delta, cited evidence, and a checked verdict.