Java Story Develop

Problem

Many Java backend or Vue full-stack requests jump from a short description directly to code changes, then run into unclear scope, unchecked schema changes, frontend/backend mismatch, or missing validation. JavaStoryDevelop targets backend or full-stack iteration by making scope, documentation, and phase state explicit, reducing rework caused by skipping analysis.

Workflow

It first inspects files such as pom.xml, build.gradle, and package.json to detect JDK, Spring Boot, ORM, database, and frontend stack. If a frontend project is detected, it asks whether to use BACKEND or FULLSTACK mode. It then selects a workflow based on change size:
- SIMPLE: small changes with a single execution document
- QUICK: normal iteration with analysis, design, and implementation
- FULL: complex refactors with clarification, design review, and feedback
It uses context.json to track phase, branch, and project environment, and can save project memory.

Notes

It works best as a process constraint, not a replacement for code review, tests, or database change approval. For external systems, multi-module refactors, or data migrations, human confirmation is still needed. Without memory or database MCP tools, fall back to full detection and let the main agent perform critical checks.