musubix3 0.1.5 → 0.1.6

package/.github/plugin/marketplace.json

@@ -3,13 +3,13 @@
   "owner": { "name": "nahisaho" },
   "metadata": {
     "description": "GitHub Copilot CLI specification-driven development skills",
-    "version": "0.1.5"
+    "version": "0.1.6"
   },
   "plugins": [
     {
       "name": "musubix3",
       "source": ".",
-      "version": "0.1.5",
+      "version": "0.1.6",
       "description": "Evidence-driven SDD without duplicating native Copilot capabilities."
     }
   ]

package/.github/skills/sdd-change/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: sdd-change
-description: "Use for feature additions, behavior changes, bug fixes, refactoring with observable impact, or any request that must propagate through requirements, design, code, tests, traceability, and quality evidence. 機能追加・仕様変更・バグ修正を一貫して反映するときに使用。"
+description: "Use as the MANDATORY first Skill for requests to develop, build, create, implement, add, change, or fix software, including 「開発」「作成」「実装」. Start requirements and design before code, then propagate through tests, traceability, and quality evidence. ソフトウェア開発依頼では実装前に必ず要求定義・設計から開始。"
 ---
 # Integrated change workflow / 統合変更ワークフロー
+Mandatory entrypoint: never start implementation for a natural-language development request before eliciting and validating requirements and design; skip only for explicitly requested implementation of verified, approved artifacts.
 Follow the user's input language. Use native Copilot planning, editing, research, review, security review and subagents.
-This skill coordinates SDD artifacts and checks; it is not another agent runtime.
 Record exactly one final invocation outcome with `npx musubix3 workflow-record
 sdd-change complete --status <status>`; `change-record` separately proves phases.
 Run `workflow-sanitize <copilot.jsonl> <safe.jsonl>` before review, then
@@ -29,8 +29,7 @@ Persisted monotonic order, not wall-clock time, proves these phase boundaries.
 2. Read the constitution and relevant requirements, designs, ADRs, code and tests.
 3. Run `npx musubix3 trace impact <id-or-path> --json` and, when code exists,
    `graph index` plus `graph impact <symbol-or-path> --json`.
-4. Separate confirmed intent, assumptions and open questions. Ask only questions
-   that materially affect observable behavior, safety or compatibility.
+4. Separate confirmed intent, assumptions and open questions. When material context is missing, ask exactly one highest-priority question, wait for its answer, then repeat; never batch questions or finalize requirements, design or code while blockers remain.
 
 ## 2. Update specifications first / 仕様を先に更新
 1. For new or changed observable behavior, add or revise EARS requirements and

package/.github/skills/sdd-implementation/SKILL.md

@@ -12,8 +12,11 @@ named npm packages; report a blocker if the executable is unavailable.
 After the work, run `npx musubix3 workflow-record sdd-implementation complete
 --status completed` exactly once.
 
-1. Read the approved requirement/design IDs and constitution. Use native planning
-   for small verifiable changes. Use native subagents only for independent work.
+1. Before editing implementation code, verify that approved requirements and
+   design artifacts exist and both validators pass. If either is absent or invalid,
+   stop and return to `sdd-change`, invoking `sdd-requirements` and `sdd-design`
+   as needed. Do not infer approval from a natural-language request such as
+   "develop", "build", 「開発」, 「作成」, or 「実装」.
 2. For behavior changes and bug fixes, write a meaningful failing test before
    implementation. Configure the selected command with `tddArgs` containing
    `{testId}` or `{testPath}` and a `tddReport`, or use a built-in runner adapter.

package/.github/skills/sdd-requirements/SKILL.md

@@ -13,7 +13,10 @@ After the work, run `npx musubix3 workflow-record sdd-requirements complete
 1. Inspect `.musubix/constitution.md` and the feature's existing requirements.
    If absent, preview `npx musubix3 init --dry-run` before installing.
 2. Use native planning to clarify scope, stakeholders, measurable acceptance and
-   failure behavior. Separate assumptions from confirmed requirements.
+   failure behavior. Separate assumptions from confirmed requirements. If required
+   context is missing, use native elicitation to ask exactly one highest-priority
+   question and wait for the answer before asking the next. Never batch questions.
+   Repeat until no material blocker remains; do not finalize requirements earlier.
 3. Edit `.musubix/features/<slug>/requirements.md` with headings
    `## REQ-FEATURE-001: Title`, `Priority: must|should|may`,
    `Type: functional|non-functional`, and `Statement: ...`. IDs are globally

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+## 0.1.6 - 2026-09-08
+
+- Make `sdd-change` the mandatory first Skill for natural-language software
+  development requests, elicit missing context one question at a time, and
+  require validated requirements and design before implementation may edit code.
 - Parse Surefire/Failsafe `<testcase>` elements correctly when a self-closing
   entry precedes one with `<system-out>`/`<system-err>` children, so JUnit
   identities are no longer dropped or given a neighbouring test's status.

package/README-ja.md

@@ -159,8 +159,13 @@ Copilot の提案を記号的検査で制約する構成であり、独自の「
 
 ## 開発ワークフロー
 
-通常の機能追加、仕様変更、バグ修正には `sdd-change` を使用します。
-以下の全工程を統合し、要求・設計・追跡情報が古いままの実装変更を完了扱いにしません。
+「○○を開発・作成・実装」のような自然言語依頼では、`sdd-change`を必須の
+最初のSkillとして発火させ、コード実装前に要求を確認・検証して設計を確定します。
+承認済みの要求・設計を実装する明示的な依頼だけが`sdd-implementation`へ直接進めます。
+要求または設計が存在しない、あるいは検証に失敗する場合、実装Skillは停止します。
+要求に必要なコンテキストが不足している場合は、優先度が最も高い質問を1問だけ行い、
+回答を待ってから次の1問へ進みます。質問をまとめず、未解決事項がなくなるまで
+要求を確定しません。
 
 1. ネイティブ計画・調査で意図と測定可能な受入条件を明確化。
 2. `change-record CHANGE-ID impact` を記録してから要求を編集・検証し、

package/README.md

@@ -162,9 +162,14 @@ no separate “neurosymbolic AI” model or claims of learned verification.
 
 ## Workflow
 
-For normal feature additions, behavior changes and bug fixes, use `sdd-change`.
-It coordinates the complete workflow below and refuses to call an
-implementation-only change complete while required artifacts remain stale.
+Natural-language requests such as “develop/build/create/implement X” activate
+`sdd-change` as the mandatory first Skill. It elicits and validates requirements
+and design before implementation; only an explicit request to implement existing
+approved artifacts may enter `sdd-implementation` directly. The implementation
+Skill fails closed when those validated artifacts are absent or invalid. When
+material context is missing, requirements elicitation asks one highest-priority
+question at a time and waits for the answer; it does not batch questions or
+finalize requirements while blockers remain.
 
 1. Use native planning/research to establish intent and measurable acceptance.
 2. Record `change-record CHANGE-ID impact`, then edit/validate requirements and

package/dist/packages/analysis/src/workflow.js

@@ -70,7 +70,7 @@ export async function recordWorkflow(root, event) {
     delete current.verification;
     current.events.push({
         skill: event.skill,
-        version: '0.1.5',
+        version: '0.1.6',
         provenance: 'self-reported',
         phase: event.phase,
         status: event.status,

package/dist/packages/cli/src/main.js

@@ -24,7 +24,7 @@ function pathQuery(root, query) {
     return portable(relative(root, resolve(root, query)));
 }
 export function createProgram() {
-    const program = new Command().name('musubix3').description('Evidence-driven SDD for GitHub Copilot CLI / 根拠に基づく仕様駆動開発').version('0.1.5');
+    const program = new Command().name('musubix3').description('Evidence-driven SDD for GitHub Copilot CLI / 根拠に基づく仕様駆動開発').version('0.1.6');
     program.exitOverride();
     common(program.command('init').alias('install').description('Install repository skills and SDD artifacts (preserves existing files)'))
         .option('--dry-run', 'Preview without writing').option('--force', 'Replace bundled, managed paths only')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "musubix3",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Evidence-driven specification development skills for GitHub Copilot CLI",
   "type": "module",
   "license": "MIT",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "musubix3",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "Evidence-driven SDD skills for GitHub Copilot CLI: requirements, design, traceability, implementation, quality, knowledge, formal checks and codegraph.",
   "author": { "name": "nahisaho" },
   "repository": "https://github.com/nahisaho/musubix3",