@melson/sdlc-mcp 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,16 @@
1
+ <!-- sdlc-chat-integration -->
2
+
3
+ ## Governed SDLC workflow
4
+
5
+ Use this workflow for repository changes. Ordinary questions and read-only investigation do not require a run.
6
+
7
+ 1. Start in native Codex Plan mode and call `sdlc_start` with the absolute repository root and the developer's complete request before repository inspection. For an unknown repository, explain its capability inventory and gaps, then ask only the returned questions about E2E, CI, and optional deployment. Call `sdlc_start` again with `confirmSetup=true` and a `setupDecision` matching the answers. Include every returned bootstrap task in the native plan together with the requested feature. Confirmed repositories need only the normal single call. Inspect the repository once with the returned company context and rules available. Do not edit until the developer accepts the complete plan.
8
+ 2. Implement the accepted plan in this checkout and preserve intentional local changes. During first-run bootstrap, preserve ready capabilities and create every required missing script, configuration, meaningful test layer, CI workflow, and explicitly requested deployment/rollback integration. Do not add no-op scripts, placeholder tests, blanket lint/type suppressions, or fake deployment commands. Proceed directly to `sdlc_verify`; it owns the configured test and security suite. Run a focused command only when debugging a concrete implementation problem or returned failure.
9
+ 3. Call `sdlc_verify` after implementation. On its first call, send the compact lifecycle checkpoint requested by the tool: plan summary and steps, requirements summary, design summary and test strategy, plus an honest `low`, `medium`, or `high` change-risk classification with a concrete rationale. The requirement coverage must list every requested behavior, conjunction, exception, boundary case, and compatibility constraint. Trace each item to a short exact quote from the original request, one measurable acceptance criterion, and focused test evidence. The controller rejects invented or duplicate source quotes, records the SDLC evidence, then runs all configured build, lint, type, test, and security gates concurrently where safe.
10
+ 4. Fix every returned failure in this conversation. Repeat `sdlc_verify` without the checkpoint until it passes or reaches its attempt limit. Never describe a failed or skipped gate as successful.
11
+ 5. Follow the review decision returned by verification. For a required review, ask the developer to type `/review` and choose **Review uncommitted changes**. Review every accepted criterion and independently enumerate every clause in the original request; a broad passing gate does not prove a specific behavior. Submit the summary, findings, criterion verdicts, and request coverage with `sdlc_review`. Missing or unverified request coverage blocks delivery. Fix blocking findings and verify again. When review is not required, continue without creating another agent turn.
12
+ 6. For delivery, create a `codex/` feature branch, commit and push the exact verified tree, then call `sdlc_publish`. The server creates or updates the pull request and follows required CI automatically. Validation runs finish without publication when the workspace is unchanged.
13
+ 7. Deployment approval belongs to the developer in the local dashboard. Never approve deployment through chat.
14
+
15
+ First-run onboarding uses one inventory call and one confirmed start call, then the normal verify and publish path. Later work uses three control-plane calls: start, verify, and publish. A policy-required native review adds one call. Use `sdlc_status` only for recovery, troubleshooting, or an explicit status request. Tool evidence, not model prose, decides completion.
16
+ <!-- /sdlc-chat-integration -->
package/package.json ADDED
@@ -0,0 +1,25 @@
1
+ {
2
+ "name": "@melson/sdlc-mcp",
3
+ "version": "0.1.0",
4
+ "description": "Local Codex connector for the SDLC Control Plane",
5
+ "type": "module",
6
+ "bin": {
7
+ "sdlc-mcp": "dist/cli.js"
8
+ },
9
+ "files": [
10
+ "dist",
11
+ "instructions.md",
12
+ "README.md"
13
+ ],
14
+ "scripts": {
15
+ "build": "esbuild src/cli.ts --bundle --platform=node --format=esm --outfile=dist/cli.js",
16
+ "prepack": "npm run build"
17
+ },
18
+ "engines": {
19
+ "node": ">=20"
20
+ },
21
+ "publishConfig": {
22
+ "access": "public"
23
+ },
24
+ "license": "UNLICENSED"
25
+ }