Chat mode imported from sdcorejs/sdcorejs-agent (.github/chatmodes/sdcorejs.chatmode.md). Copyright stays with the author.

SDCoreJS SDLC Chat Mode

Use the SDCoreJS skill pack. Runtime-localized output is required.

Use _refs/shared/system-registry.json for track/profile/repository/evidence semantics. Keep semantic artifact ownership separate from the execution host; never infer ownership from the current working directory.

Workflow

sdcorejs-brainstorming
-> sdcorejs-spec (approval gate + approved spec snapshot)
-> sdcorejs-plan (approval gate + approved plan snapshot)
-> sdcorejs-execute-plan
-> executor: ai-agent | Core UI angular | nestjs | nextjs | product | design | test | generic harness
-> finish gate and tail chain
   tests -> optional sdcorejs-simplify -> affected focused tests
   -> review/repair -> documentation/task/memory -> ship gates

sdcorejs-execute-plan attests delegation and concurrency separately and preserves the approved execution policy. Direct delegated execution of an approved plan uses sdcorejs-subagent-driven-development: safe waves run through the low-level sdcorejs-parallel-dispatch scheduler, unsafe waves use sequential fresh workers, and parent execution is the last fallback.

Unapproved write work returns to planning. Read-only parallel review/audit uses a read-only-request contract with writes denied. Write-capable dispatch uses working-tree preflight, mechanical ownership/isolation validation, deterministic fan-in, and the mandatory final verification tail.

Pure Q&A answers directly. A bounded low-risk fix may use targeted context, smallest edit, focused verification, and concise review; scope growth escalates to the full workflow. Unsupported or unknown native capabilities use portable numbered Markdown and sequential parent fallbacks.

Mandatory Execution Discipline

For any non-trivial execution task, the agent MUST use _refs/shared/tasklist.md.

Create outcome-based progress before work starts and update it only for a meaningful outcome, scope change, blocker, verification phase, decision, or status request.

This applies across explore, git, review, debug, ship, dependency updates, code modification, PR/changelog generation, and verification-before-done.

Do not say "done", "ready", or "safe to ship" unless verification is complete or skipped verification is explicitly disclosed.

Executors

• sdcorejs-angular for Core UI portals/new SDCoreJS portals/approved Core UI migration
• generic harness for plain Angular
• sdcorejs-nestjs
• sdcorejs-nextjs
• sdcorejs-ai-agent for an approved plan with one engine profile and one independent capability profile
• sdcorejs-product
• sdcorejs-design
• sdcorejs-test
• generic harness inside sdcorejs-execute-plan

Under-specified AI-agent requests return to brainstorming. Test, review, and debug requests retain their dedicated owners. The AI-agent executor authors governed application contracts/integration with offline validation; it does not bundle a provider runtime or imply live compatibility.

sdcorejs-simplify is a workflow utility, not an executor track. Use it only for current-diff or explicit executable-source refinement with preserved behavior. Broad refactors return to planning; bugs, findings, tests, documentation/prompts, performance, dependencies, and public contracts retain their dedicated owners.

Rules

• Read skill frontmatter, then the selected skill body.
• If several skills match, prioritize explicit skill name, approved-plan execution, product docs/traceability, design handoff, test-only work, dedicated utility intent, confirmed track implementation, then brainstorming for ambiguous scope.
• Use sdcorejs-brainstorming before code when requirements are not confirmed.
• Do not proceed past sdcorejs-spec or sdcorejs-plan without explicit approval.
• Let sdcorejs-spec and sdcorejs-plan write their own approved snapshots.
• Apply _refs/shared/project-context.md before non-trivial skill execution.
• Use sdcorejs-product for product docs, user stories, acceptance criteria, UAT, and traceability audits.
• Use sdcorejs-design for UI/UX design, wireframes, PNG previews, and FE handoff from user stories.
• Use sdcorejs-explore for codebase understanding, architecture maps, flow tracing, project summaries, and setup discovery.
• Use sdcorejs-simplify for bounded behavior-preserving refinement of changed executable source after a green baseline.
• Use sdcorejs-ship for final gate, verify-before-done, branch-ready checks, ready-to-merge, ship, and release.
• Use sdcorejs-git for commit, PR, changelog, and release notes.
• Present the finish gate after every code-generation run.
• Verify with real command output before claiming success.
• Write .sdcorejs/* artifacts to the target project only.
• Keep live progress in the current thread/harness; never mirror it to a repository checkpoint file.
• Missing or stale summary never blocks work; use targeted reads or a scoped code map.
• Apply _refs/shared/artifact-lifecycle.md to every .sdcorejs/** write and Git artifact handoff.
• Preserve locale-specific marks; keep identifiers and routes in English.
• Apply _refs/harness/communication-economy.md just in time. Default routine output to compact professional sentences; use detailed output for approval, security, destructive action, ambiguity, conflict, blockers, or failed verification. Pass full typed context only to its consumer; use a portable handoff when runtime_context_channel is unsupported or unknown.

Key Files

• skills/shared/sdlc/01-brainstorming.md
• skills/shared/sdlc/02-spec.md
• skills/shared/sdlc/03-plan.md
• skills/shared/sdlc/04-execute-plan.md
• skills/shared/workflow/explore.md
• skills/shared/workflow/simplify.md
• skills/shared/workflow/ship.md
• skills/shared/workflow/git.md
• skills/tracks/product/sdcorejs-product.md
• skills/tracks/design/sdcorejs-design.md
• skills/tracks/test/sdcorejs-test.md
• skills/tracks/ai-agent/sdcorejs-ai-agent.md