v1.5.0 - Plan to Issue workflow
Agentic SDLC MCP v1.5.0
v1.5.0 completes the ROADMAP Plan-to-Issue workflow. AI coding agents can now turn a contextual SDLC plan into structured, reviewable GitHub issue drafts without manually rewriting the plan, preview the exact batch safely, and retain actionable evidence when only part of a live batch succeeds.
Highlights
Structured Plan-to-Issue workflow
plan_from_contextnow returns 3-5 structuredissueDraftsfor every supported work type.- Each draft includes:
- executable title
- Markdown issue body
- labels confirmed to exist in the target repository
- SDLC phase
- acceptance criteria
- risk level
- source goal for traceability
- Complete drafts can be passed directly to
create_issue_set.issues, including through strict MCP clients. - Generated titles are bounded to GitHub's 256-character limit.
- Repository labels are matched case-insensitively while preserving their actual GitHub spelling.
Reviewable and safer issue batches
create_issue_setstill defaults todryRun: true.- Dry-run output now includes:
- exact target repository
- final issue titles
- labels
- bounded body summaries
- warnings for missing labels, short bodies, and overlong titles
- Preview output explicitly confirms that no GitHub write API was called.
- Live batches continue after an individual issue fails.
- Results retain both successful issue numbers/URLs/labels and safe failure reasons.
- Failures include a zero-based
inputIndex, so duplicate titles can be located and retried without duplicating successful issues. - Raw GitHub response bodies are not exposed in failure output.
Better repository briefing packets
repo_contextnow includes boundedreadmeSummaryandpackageJsonSummaryvalues instructuredContent.- Missing, invalid, scalar, or array-shaped package manifests degrade cleanly in both Markdown and structured output.
- Package summaries are capped at 2,000 characters.
- Common package scripts are capped at 300 characters per command and 1,200 characters total.
- A legitimate package.json
_rawfield is no longer confused with internal parse-failure state.
Version and documentation
- Package, lockfile, and MCP runtime version are aligned at
1.5.0. - Added a regression test that checks runtime/package version consistency.
- Updated English and Chinese README tool contracts.
- Marked ROADMAP v1.5 as complete.
Compatibility
- Existing
repo_context,plan_from_context, andcreate_issue_setfields remain available. - New structured fields are additive.
- Existing issue inputs continue to work.
- This release does not add auto-merge, force-push, branch deletion, or arbitrary repository code-writing capabilities.
Verification
- 16 test files, 268 tests passed
- Coverage:
- statements: 84.74%
- branches: 82.00%
- functions: 83.51%
- lines: 84.32%
- TypeScript build and typecheck passed
- MCP smoke registration passed
- npm package dry-run passed
- production dependency audit: 0 vulnerabilities
- PR CI and post-merge
mainCI passed - independent final reviewer found no actionable regressions
Upgrade
npm install --global agentic-sdlc-mcp@1.5.0MCP configurations using npx -y agentic-sdlc-mcp will resolve the latest published version after npm propagation and client restart.
Full changes: v1.4.0...v1.5.0