sdcorejs-using-skills

name	sdcorejs-using-skills
description	Session bootstrap and dispatch guide for sdcorejs skills. Use at session start, onboarding/help/list-skill requests, or any request matching an sdcorejs skill. Establishes brainstorming -> spec -> plan -> execute-plan -> finish flow, approval gates, track selection, generic fallback, and invoke-relevant-skill-first discipline. Runtime-localized.
allowed-tools	Read, Glob

Using sdcorejs Skills

Shared Protocols

Before executing this skill:

1. Read and apply _refs/shared/tasklist.md for non-trivial execution tasks.
2. Read and apply _refs/shared/persona.md if a project persona exists.
3. Read and apply _refs/shared/project-context.md for project memory, resume checkpoints, summaries, specs/plans, tasks, and relevant memories.
4. Current user request, current files, diffs, logs, failing tests, and command output override stored context.
5. Before presenting user-facing choices, approval gates, yes/no questions, or mode selections, read and apply _refs/shared/user-choice-prompt.md so options are presented as sequential numbered choices.

Rule

When a request matches a skill, invoke that skill before responding. Skills decide how to explore, plan, build, verify, and ship.

Dispatch

1. Match the request against each skill description.
2. If several match, apply the priority list below before reading a body.
3. Read the chosen skill body and follow it.
4. If nothing matches, answer briefly from this bootstrap and route to sdcorejs-brainstorming.

Priority when several skills match:

1. Explicit skill name from the user.
2. Approved spec/plan continuation: sdcorejs-execute-plan.
3. Product docs and traceability: sdcorejs-product.
4. Design handoff artifacts: sdcorejs-design.
5. Test-only work: sdcorejs-test, except failing-test root cause/fix goes to sdcorejs-debug.
6. Dedicated utility intent: sdcorejs-explore, sdcorejs-documentation, sdcorejs-review, sdcorejs-debug, sdcorejs-ship, or sdcorejs-git.
7. Whole app/system build intent: sdcorejs-solution-builder.
8. Confirmed track implementation: sdcorejs-angular, sdcorejs-nestjs, or sdcorejs-nextjs.
9. Open-ended, ambiguous, or under-specified scope: sdcorejs-brainstorming.

Tracks

Track	Executor
Angular portal	sdcorejs-angular
NestJS backend	sdcorejs-nestjs
Next.js site	sdcorejs-nextjs
Product / PO traceability	sdcorejs-product
Design / FE handoff	sdcorejs-design
Tests	sdcorejs-test
Unknown / unsupported stack	sdcorejs-execute-plan generic harness fallback

The product track is first-class: feature docs, user stories, acceptance criteria, UAT, and traceability audits execute through sdcorejs-product.

The design track is first-class: UI/UX design, wireframes, screen flows, PNG previews, and FE handoff artifacts execute through sdcorejs-design.

The test track is first-class: test-only plans execute through sdcorejs-test, not through the app write-code skills.

Workflow

Session start
  -> read .sdcorejs/tasks/current-session.md when present
  -> sdcorejs-explore when project context is needed
Request
  -> sdcorejs-brainstorming       (explore if needed, then confirm blockers)
  -> sdcorejs-spec                (write spec + approval gate + approved spec snapshot)
  -> sdcorejs-plan                (write plan + approval gate + approved plan snapshot)
  -> sdcorejs-execute-plan        (detect track, always ask sequential vs parallel)
  -> track executor or harness    (angular | nestjs | nextjs | product | design | test | generic)
  -> finish gate and mandatory tail

sdcorejs-execute-plan always asks whether the user wants sequential or parallel execution before code/test generation. If parallel is chosen, it runs sdcorejs-parallel-dispatch first and only fans out when that gate says it is safe.

Non-negotiables

• Confirm requirements before spec. Do not generate code from an unconfirmed scope.
• Keep the two approval gates: spec approval and plan approval. Silence is not approval.
• sdcorejs-spec and sdcorejs-plan write their own approved snapshots before moving forward.
• Apply _refs/shared/project-context.md before any non-trivial skill execution so direct-triggered skills load summaries, checkpoints, specs/plans, tasks, and relevant memories.
• Use sdcorejs-execute-plan after plan approval; it owns track detection, product-track routing, design-track routing, test-track routing, generic harness fallback, and the parallel/sequential question.
• Present the finish gate after every code-generation run.
• Before any choice, approval gate, yes/no question, or mode selection, apply _refs/shared/user-choice-prompt.md so the user can answer with a number.
• Run verification before claiming pass, fixed, built, or done.
• For long or interruptible work, mirror visible Tasks progress to the ignored local .sdcorejs/tasks/current-session.md; do not commit live session state.
• Match the user's language at runtime; keep identifiers and route paths in English.

First step guidance

• Open-ended idea or incomplete scope: sdcorejs-brainstorming.
• Concrete feature request: sdcorejs-brainstorming in confirm mode.
• Product docs, user stories, acceptance criteria, UAT, or requirement/implementation/test consistency: sdcorejs-product.
• Design docs, wireframes, mockups, PNG previews, screen flows, or FE handoff from user stories: sdcorejs-design.
• Code comments, user guides, technical docs, or documentation rewrite/improve/structure/summarize/convert/standardize work: sdcorejs-documentation.
• Project summary, code-map, trace-flow, env setup, recovery, persona, or memories: sdcorejs-explore.
• Existing site audit: sdcorejs-review.
• Test request: sdcorejs-test for direct test work, or sdcorejs-brainstorming first if cases/assertions are not confirmed.
• Approved plan: sdcorejs-execute-plan.

Cross-references

• sdcorejs-brainstorming
• sdcorejs-spec
• sdcorejs-plan
• sdcorejs-execute-plan
• sdcorejs-product
• sdcorejs-design
• sdcorejs-test
• sdcorejs-documentation
• sdcorejs-parallel-dispatch