specdojo 0.4.6 → 0.5.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.
- package/.github/agents/specdojo-orchestrator.md +14 -9
- package/CHANGELOG.md +62 -0
- package/dist/catalog/document-target.js +75 -0
- package/dist/commands/agent.js +2 -80
- package/dist/commands/init.js +3 -0
- package/dist/commands/night-orchestrator.js +33 -4
- package/dist/dashboard/dashboard.js +5 -6
- package/dist/dashboard/timeline-build.js +5 -1
- package/dist/dashboard/timeline.js +6 -3
- package/dist/docs/yaml-pages.js +17 -17
- package/dist/exec/agent-config.js +28 -16
- package/dist/exec/agent-plan.js +108 -0
- package/dist/exec/commands.js +3 -3
- package/dist/exec/core.js +2 -0
- package/dist/exec/grade-checkpoint.js +12 -0
- package/dist/exec/pipeline-state.js +5 -2
- package/dist/exec/plans-core.js +7 -67
- package/dist/exec/plans-generation.js +28 -7
- package/dist/exec/plans-grade-findings.js +16 -0
- package/dist/exec/plans-planning.js +43 -0
- package/dist/exec/plans-storage.js +5 -2
- package/dist/exec/project.js +4 -1
- package/dist/exec/register.js +82 -6
- package/dist/exec/repo-integration-sync.js +9 -0
- package/dist/exec/repo-integration.js +17 -2
- package/dist/exec/repo-trace.js +17 -4
- package/dist/exec/results.js +2 -0
- package/dist/exec/run/lifecycle-commands.js +2 -0
- package/dist/exec/run/register-core.js +11 -0
- package/dist/exec/run/register-mode.js +19 -1
- package/dist/exec/run/register-resume.js +23 -0
- package/dist/exec/run/register-state.js +4 -1
- package/dist/exec/run/register-worktree.js +28 -1
- package/dist/exec/run/schedule-prepare.js +7 -1
- package/dist/exec/strategy.js +2 -0
- package/dist/exec/task-repos.js +18 -4
- package/dist/exec/worktree-command.js +8 -1
- package/dist/exec/worktree-ops-commit.js +7 -1
- package/dist/exec/worktree-ops-merge.js +40 -1
- package/dist/grade/apply.js +13 -7
- package/dist/grade/command-inspect.js +2 -1
- package/dist/grade/command-run.js +39 -0
- package/dist/grade/grade.js +3 -1
- package/dist/grade/markdown.js +11 -6
- package/dist/grade/pipeline-state.js +8 -6
- package/dist/grade/plan.js +14 -10
- package/dist/grade/run.js +307 -0
- package/dist/grade/target-discovery.js +1 -1
- package/dist/grade/targets.js +44 -22
- package/dist/register/approach.js +35 -0
- package/dist/register/catalog-status.js +49 -0
- package/dist/register/core.js +5 -0
- package/dist/register/create-commands.js +83 -5
- package/dist/register/deliverable-target.js +215 -0
- package/dist/register/dependency.js +123 -0
- package/dist/register/derivation.js +2 -2
- package/dist/register/epic.js +42 -0
- package/dist/register/event-merge.js +5 -2
- package/dist/register/events.js +8 -0
- package/dist/register/external-project.js +4 -0
- package/dist/register/item.js +18 -0
- package/dist/register/maintenance-commands.js +7 -1
- package/dist/register/planning.js +37 -0
- package/dist/register/register.js +5 -1
- package/dist/register/renumber.js +12 -4
- package/dist/register/views.js +55 -4
- package/dist/review/grade.js +19 -17
- package/dist/schedule/schedule.js +3 -1
- package/dist/schedule/strategy-generate-scope.js +5 -1
- package/dist/schedule/strategy-generate.js +1 -0
- package/dist/schedule/strategy-profiles.js +1 -1
- package/dist/shared/agent-plan.js +1 -0
- package/dist/shared/agent-types.js +3 -0
- package/dist/shared/grade-result.js +23 -5
- package/dist/shared/markdownlint-config.js +38 -0
- package/dist/shared/markdownlint-scaffold.js +2 -9
- package/dist/shared/provider-scaffold.js +5 -3
- package/dist/shared/specdojo-config.js +10 -3
- package/dist/shared/specdojo-gitignore.js +4 -0
- package/dist/specdojo.js +5 -1
- package/docs/ja/specdojo/exec-templates/xep-catalog-planning-template.md +24 -0
- package/docs/ja/specdojo/exec-templates/xep-strategy-planning-template.md +24 -0
- package/docs/ja/specdojo/exec-templates/xrp-freeform-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-fully-guided-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-recipe-guided-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-recipe-maintenance-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-retrofit-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-rulebook-maintenance-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-sample-maintenance-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-template-maintenance-template.md +2 -2
- package/docs/ja/specdojo/exec-templates/xrp-template.md +2 -2
- package/docs/ja/specdojo/guides/docs-editing-guide.md +14 -1
- package/docs/ja/specdojo/guides/docs-structure-guide.md +10 -8
- package/docs/ja/specdojo/guides/exec-config-guide.md +44 -12
- package/docs/ja/specdojo/guides/exec-operation-guide.md +20 -15
- package/docs/ja/specdojo/guides/orchestrator-operation-guide.md +19 -1
- package/docs/ja/specdojo/guides/plan-result-lifecycle-guide.md +3 -1
- package/docs/ja/specdojo/guides/practice-system-composition-guide.md +2 -0
- package/docs/ja/specdojo/guides/quick-start-guide.md +59 -16
- package/docs/ja/specdojo/guides/register-operation-guide.md +44 -15
- package/docs/ja/specdojo/guides/remote-host-development-guide.md +15 -1
- package/docs/ja/specdojo/guides/review-guide.md +2 -2
- package/docs/ja/specdojo/guides/ryu-guide.md +12 -0
- package/docs/ja/specdojo/guides/specdojo-overview-guide.md +16 -16
- package/docs/ja/specdojo/guides/timeline-design-guide.md +37 -33
- package/docs/ja/specdojo/recipes/tsd-recipe.md +198 -0
- package/docs/ja/specdojo/references/command-reference.md +92 -29
- package/docs/ja/specdojo/references/specdojo-config-reference.md +49 -16
- package/docs/ja/specdojo/rulebooks/atc-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/atc-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/bac-rulebook.md +5 -4
- package/docs/ja/specdojo/rulebooks/bdd-rulebook.md +3 -2
- package/docs/ja/specdojo/rulebooks/bds-rulebook.md +4 -3
- package/docs/ja/specdojo/rulebooks/bes-index-rulebook.md +8 -7
- package/docs/ja/specdojo/rulebooks/bes-rulebook.md +4 -3
- package/docs/ja/specdojo/rulebooks/bps-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/br-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/ccd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cdfd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cdfd-overview-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cdfd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cdfd-uc-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cdsd-rulebook.md +3 -2
- package/docs/ja/specdojo/rulebooks/cld-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/cnd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cnd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cop-index-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/cop-rulebook.md +3 -2
- package/docs/ja/specdojo/rulebooks/cpd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cpd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cstd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cxd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/cxd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/dct-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/dct-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/dec-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/dmd-index-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/dmd-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/etc-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/etc-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/gl-rulebook.md +9 -6
- package/docs/ja/specdojo/rulebooks/ifd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/ifx-api-rulebook.md +3 -1
- package/docs/ja/specdojo/rulebooks/ifx-cmd-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/ifx-file-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/ifx-index-rulebook.md +2 -0
- package/docs/ja/specdojo/rulebooks/ifx-msg-rulebook.md +4 -2
- package/docs/ja/specdojo/rulebooks/imp-business-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/imp-data-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/imp-interface-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/imp-operations-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/imp-test-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/itc-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/itc-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/mip-index-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/mm-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/mtp-rulebook.md +4 -3
- package/docs/ja/specdojo/rulebooks/nfr-availability-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/nfr-index-rulebook.md +10 -9
- package/docs/ja/specdojo/rulebooks/nfr-integrity-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/nfr-maintainability-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/nfr-operations-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/nfr-performance-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/nfr-reliability-rulebook.md +10 -9
- package/docs/ja/specdojo/rulebooks/nfr-security-safety-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/nfr-usability-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/ntp-rulebook.md +7 -6
- package/docs/ja/specdojo/rulebooks/opd-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/opd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/opr-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/opr-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/otp-index-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/otp-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/pjr-rulebook.md +56 -36
- package/docs/ja/specdojo/rulebooks/pm-change-request-log-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-communication-plan-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-issue-log-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-members-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-organization-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-plan-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-quality-management-plan-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-raci-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-risk-register-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pm-roles-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/pr-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-assumptions-constraints-dependencies-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-charter-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-comparison-of-alternatives-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-issues-and-approach-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-overview-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-scope-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-stakeholder-register-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/prj-success-criteria-and-acceptance-criteria-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/sac-rulebook.md +3 -2
- package/docs/ja/specdojo/rulebooks/sch-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/sf-index-rulebook.md +7 -6
- package/docs/ja/specdojo/rulebooks/sf-rulebook.md +4 -3
- package/docs/ja/specdojo/rulebooks/sld-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/stc-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/stc-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/stsd-mermaid-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/stsd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/sysd-critical-flows-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/sysd-cross-cutting-policy-rulebook.md +9 -8
- package/docs/ja/specdojo/rulebooks/sysd-index-rulebook.md +2 -1
- package/docs/ja/specdojo/rulebooks/sysd-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/tml-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/trc-requirements-to-specs-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/trc-requirements-to-tests-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/tsd-index-rulebook.md +80 -61
- package/docs/ja/specdojo/rulebooks/tsd-rulebook.md +111 -63
- package/docs/ja/specdojo/rulebooks/tsp-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/uis-rulebook.md +3 -2
- package/docs/ja/specdojo/rulebooks/utc-index-rulebook.md +1 -0
- package/docs/ja/specdojo/rulebooks/utc-rulebook.md +1 -0
- package/docs/ja/specdojo/samples/atc-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/atc-sample.md +1 -1
- package/docs/ja/specdojo/samples/bac-sample.md +1 -1
- package/docs/ja/specdojo/samples/bdd-sample.yaml +1 -1
- package/docs/ja/specdojo/samples/bds-sample.md +1 -1
- package/docs/ja/specdojo/samples/bes-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/bes-sample.md +1 -1
- package/docs/ja/specdojo/samples/ccd-sample.md +1 -1
- package/docs/ja/specdojo/samples/cdfd-sample.md +1 -1
- package/docs/ja/specdojo/samples/cdfd-uc-sample.md +1 -1
- package/docs/ja/specdojo/samples/cdsd-sample.md +1 -1
- package/docs/ja/specdojo/samples/cld-sample.md +1 -1
- package/docs/ja/specdojo/samples/cnd-sample.md +1 -1
- package/docs/ja/specdojo/samples/cop-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/cop-sample.md +1 -1
- package/docs/ja/specdojo/samples/cpd-sample.md +1 -1
- package/docs/ja/specdojo/samples/cstd-sample.md +1 -1
- package/docs/ja/specdojo/samples/cxd-sample.md +1 -1
- package/docs/ja/specdojo/samples/dmd-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/dmd-sample.md +1 -1
- package/docs/ja/specdojo/samples/etc-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/etc-sample.md +1 -1
- package/docs/ja/specdojo/samples/gl-sample.yaml +2 -0
- package/docs/ja/specdojo/samples/ifd-sample.md +1 -1
- package/docs/ja/specdojo/samples/ifx-api-sample.yaml +1 -0
- package/docs/ja/specdojo/samples/ifx-cmd-sample.yaml +1 -1
- package/docs/ja/specdojo/samples/ifx-file-sample.md +1 -1
- package/docs/ja/specdojo/samples/ifx-index-sample.yaml +1 -0
- package/docs/ja/specdojo/samples/ifx-msg-sample.yaml +2 -1
- package/docs/ja/specdojo/samples/itc-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/itc-sample.md +1 -1
- package/docs/ja/specdojo/samples/mtp-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-availability-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-integrity-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-maintainability-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-operations-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-performance-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-reliability-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-security-safety-sample.md +1 -1
- package/docs/ja/specdojo/samples/nfr-usability-sample.md +1 -1
- package/docs/ja/specdojo/samples/ntp-sample.md +1 -1
- package/docs/ja/specdojo/samples/opd-sample.md +1 -1
- package/docs/ja/specdojo/samples/opr-sample.md +1 -1
- package/docs/ja/specdojo/samples/otp-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/otp-sample.md +1 -1
- package/docs/ja/specdojo/samples/prj-stakeholder-register-sample.md +1 -1
- package/docs/ja/specdojo/samples/sac-sample.md +1 -1
- package/docs/ja/specdojo/samples/sf-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/sf-sample.md +1 -1
- package/docs/ja/specdojo/samples/sld-sample.md +1 -1
- package/docs/ja/specdojo/samples/stc-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/stc-sample.md +1 -1
- package/docs/ja/specdojo/samples/stsd-sample.md +1 -1
- package/docs/ja/specdojo/samples/sysd-critical-flows-sample.md +1 -1
- package/docs/ja/specdojo/samples/sysd-cross-cutting-policy-sample.md +1 -1
- package/docs/ja/specdojo/samples/sysd-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/tsd-index-sample.md +22 -16
- package/docs/ja/specdojo/samples/tsd-sample.md +241 -21
- package/docs/ja/specdojo/samples/tsp-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/uis-sample.md +1 -1
- package/docs/ja/specdojo/samples/utc-index-sample.md +1 -1
- package/docs/ja/specdojo/samples/utc-sample.md +1 -1
- package/docs/ja/specdojo/standards/document-metadata-standard.md +28 -3
- package/docs/ja/specdojo/standards/id-and-file-naming-standard.md +2 -0
- package/docs/ja/specdojo/standards/rulebook-authoring-standard.md +16 -11
- package/docs/ja/specdojo/standards/sample-authoring-standard.md +1 -0
- package/docs/ja/specdojo/templates/ifx-cmd-template.yaml +1 -1
- package/docs/ja/specdojo/templates/pjr-dependent-items-template.md +22 -0
- package/docs/ja/specdojo/templates/pjr-epic-items-template.md +22 -0
- package/docs/ja/specdojo/templates/pjr-epic-template.md +44 -0
- package/docs/ja/specdojo/templates/pjr-index-template.md +4 -2
- package/docs/specdojo/schemas/v1/bdd.schema.yaml +1 -1
- package/docs/specdojo/schemas/v1/deliverable-frontmatter.schema.yaml +24 -16
- package/docs/specdojo/schemas/v1/exec-common.schema.yaml +4 -1
- package/docs/specdojo/schemas/v1/exec-plan-frontmatter.schema.yaml +1 -1
- package/docs/specdojo/schemas/v1/gl.schema.yaml +8 -0
- package/docs/specdojo/schemas/v1/grade-pipeline-state.schema.yaml +1 -1
- package/docs/specdojo/schemas/v1/ifx-cmd.schema.yaml +5 -1
- package/docs/specdojo/schemas/v1/pipeline-state.schema.yaml +2 -1
- package/docs/specdojo/schemas/v1/register-events.schema.yaml +20 -0
- package/docs/specdojo/schemas/v1/register-item-frontmatter.schema.yaml +73 -4
- package/docs/specdojo/schemas/v1/rulebook-frontmatter.schema.yaml +5 -0
- package/docs/specdojo/schemas/v1/specdojo-config.schema.yaml +21 -3
- package/package.json +2 -2
- package/templates/antigravity/orchestrator.md +14 -9
- package/templates/claude/agents/specdojo-orchestrator.md +14 -9
- package/templates/codex/agents/specdojo-orchestrator.toml +14 -9
- package/templates/codex/orchestrator.md +14 -9
- package/templates/copilot/README.md +2 -1
- package/templates/devcontainer/devcontainer.json +1 -0
- package/templates/init-agent-members.yaml +46 -3
- package/templates/opencode/README.md +118 -14
- package/templates/opencode/agents/specdojo-orchestrator.md +15 -10
- package/templates/opencode/opencode.json +25 -0
|
@@ -1,5 +1,20 @@
|
|
|
1
1
|
$schema: "https://json-schema.org/draft/2020-12/schema"
|
|
2
2
|
title: Deliverables Front Matter
|
|
3
|
+
$defs:
|
|
4
|
+
deliverableType:
|
|
5
|
+
type: string
|
|
6
|
+
enum:
|
|
7
|
+
- project # プロジェクトの管理文書
|
|
8
|
+
- requirement # システム機能・非機能要件・受入基準
|
|
9
|
+
- glossary # 用語集
|
|
10
|
+
- flow # 業務フロー・プロセス仕様
|
|
11
|
+
- rule # 業務ルール仕様
|
|
12
|
+
- data # データ仕様
|
|
13
|
+
- ui # 画面・帳票仕様
|
|
14
|
+
- api # API・外部 I/F 仕様
|
|
15
|
+
- architecture # アーキテクチャ設計
|
|
16
|
+
- test # テスト仕様・設計
|
|
17
|
+
- operations # 運用設計・手順
|
|
3
18
|
# SpecDojo が所有する frontmatter は `specdojo:` 名前空間配下に置く。
|
|
4
19
|
# トップレベルは第三者ツール(VitePress 等)のキーを許容するため制限しない。
|
|
5
20
|
type: object
|
|
@@ -16,22 +31,12 @@ properties:
|
|
|
16
31
|
- rulebook
|
|
17
32
|
properties:
|
|
18
33
|
type:
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
- project # プロジェクト文書全般
|
|
26
|
-
# プロダクト仕様文書
|
|
27
|
-
- flow # 業務フロー・プロセス仕様
|
|
28
|
-
- rule # 業務ルール仕様
|
|
29
|
-
- data # データ仕様
|
|
30
|
-
- ui # 画面・帳票仕様
|
|
31
|
-
- api # API・外部I/F仕様
|
|
32
|
-
- architecture # アーキテクチャ設計
|
|
33
|
-
- test # テスト仕様・設計
|
|
34
|
-
- operations # 運用設計・手順
|
|
34
|
+
anyOf:
|
|
35
|
+
- $ref: "#/$defs/deliverableType"
|
|
36
|
+
- type: string
|
|
37
|
+
enum:
|
|
38
|
+
- template # テンプレート自身のメタ情報
|
|
39
|
+
- sample # 非推奨。rulebook を持つ sample は宣言された成果物 type に移行する。
|
|
35
40
|
description: "仕様の種別(rulebook/guide/standard は各専用スキーマを使用)"
|
|
36
41
|
rulebook:
|
|
37
42
|
$ref: "./common-frontmatter.schema.yaml#/$defs/rulebookRef"
|
|
@@ -60,6 +65,9 @@ properties:
|
|
|
60
65
|
item_type:
|
|
61
66
|
$ref: "./register-item-frontmatter.schema.yaml#/$defs/ItemType"
|
|
62
67
|
description: "プロジェクト登録項目の種別。pjr-*-template で使用する。"
|
|
68
|
+
track:
|
|
69
|
+
$ref: "./register-item-frontmatter.schema.yaml#/$defs/Track"
|
|
70
|
+
description: "epic が担う track。定義の検証は register コマンドが行う。"
|
|
63
71
|
item_status:
|
|
64
72
|
$ref: "./register-item-frontmatter.schema.yaml#/$defs/ItemStatus"
|
|
65
73
|
description: "登録項目の処理状態。文書成熟度の status とは別の状態軸。"
|
|
@@ -52,6 +52,8 @@ $defs:
|
|
|
52
52
|
"recipe-guided",
|
|
53
53
|
"freeform",
|
|
54
54
|
"bootstrap",
|
|
55
|
+
"catalog-planning",
|
|
56
|
+
"strategy-planning",
|
|
55
57
|
"rulebook-authoring",
|
|
56
58
|
"recipe-authoring",
|
|
57
59
|
"sample-authoring",
|
|
@@ -66,7 +68,8 @@ $defs:
|
|
|
66
68
|
"bootstrap-finalize",
|
|
67
69
|
]
|
|
68
70
|
description: >
|
|
69
|
-
How the task is carried out.
|
|
71
|
+
How the task is carried out. catalog-planning and strategy-planning create a catalog
|
|
72
|
+
or schedule strategy from register-only domain:<id> / track:<id> targets. fully-guided/recipe-guided/freeform describe how strictly
|
|
70
73
|
the agent follows reference materials (rulebook/recipe/sample/template) when working on
|
|
71
74
|
a deliverable. bootstrap authors the deliverable and its full reference set
|
|
72
75
|
(rulebook/recipe/sample/template) together in one task as a mutually consistent whole;
|
|
@@ -110,7 +110,7 @@ properties:
|
|
|
110
110
|
minLength: 1
|
|
111
111
|
minItems: 1
|
|
112
112
|
description: >
|
|
113
|
-
|
|
113
|
+
Document IDs, or domain:<id> / track:<id> for register planning approaches. Existing documents are resolvable via the
|
|
114
114
|
doc index. For deliverable work, the first entry is the target deliverable and subsequent
|
|
115
115
|
entries are reference materials the approach may modify or confirm. For *-authoring
|
|
116
116
|
register tasks, the entry is an intentionally not-yet-existing kata id; read-only
|
|
@@ -4,10 +4,18 @@ type: object
|
|
|
4
4
|
additionalProperties: false
|
|
5
5
|
required:
|
|
6
6
|
- id
|
|
7
|
+
- type
|
|
8
|
+
- rulebook
|
|
7
9
|
- title
|
|
8
10
|
- locale
|
|
9
11
|
- terms
|
|
10
12
|
properties:
|
|
13
|
+
type:
|
|
14
|
+
type: string
|
|
15
|
+
const: glossary
|
|
16
|
+
rulebook:
|
|
17
|
+
type: string
|
|
18
|
+
pattern: "^((?:[a-z][a-z0-9-]*:)?[a-z0-9][a-z0-9-]*-rulebook|none)$"
|
|
11
19
|
id:
|
|
12
20
|
type: string
|
|
13
21
|
pattern: "^([a-z0-9-]+:)?gl-[a-z0-9-]+$"
|
|
@@ -26,7 +26,7 @@ properties:
|
|
|
26
26
|
minLength: 1
|
|
27
27
|
type:
|
|
28
28
|
type: string
|
|
29
|
-
enum: ["
|
|
29
|
+
enum: ["api", "template"]
|
|
30
30
|
status:
|
|
31
31
|
type: string
|
|
32
32
|
enum: ["draft", "ready", "deprecated"]
|
|
@@ -46,6 +46,10 @@ properties:
|
|
|
46
46
|
metadata_template:
|
|
47
47
|
type: object
|
|
48
48
|
additionalProperties: true
|
|
49
|
+
properties:
|
|
50
|
+
type:
|
|
51
|
+
type: string
|
|
52
|
+
const: api
|
|
49
53
|
|
|
50
54
|
command:
|
|
51
55
|
type: object
|
|
@@ -81,8 +81,9 @@ $defs:
|
|
|
81
81
|
required: [status, commit, merged_at]
|
|
82
82
|
properties:
|
|
83
83
|
status:
|
|
84
|
+
# branch-only is successful handling without a merge; commit and merged_at stay null.
|
|
84
85
|
type: string
|
|
85
|
-
enum: [pending, merged, unchanged, failed]
|
|
86
|
+
enum: [pending, merged, unchanged, branch-only, failed]
|
|
86
87
|
# Merge commit on the integration target. Null for the project repository (the merge commit
|
|
87
88
|
# contains this state) and for repositories that are not merged.
|
|
88
89
|
commit:
|
|
@@ -33,6 +33,22 @@ $defs:
|
|
|
33
33
|
- migrate
|
|
34
34
|
|
|
35
35
|
RegisterEventChange:
|
|
36
|
+
allOf:
|
|
37
|
+
- if:
|
|
38
|
+
required: [field]
|
|
39
|
+
properties:
|
|
40
|
+
field:
|
|
41
|
+
const: type
|
|
42
|
+
then:
|
|
43
|
+
properties:
|
|
44
|
+
from:
|
|
45
|
+
anyOf:
|
|
46
|
+
- $ref: "./register-item-frontmatter.schema.yaml#/$defs/ItemType"
|
|
47
|
+
- enum: ["", "-", "_TODO_"]
|
|
48
|
+
to:
|
|
49
|
+
anyOf:
|
|
50
|
+
- $ref: "./register-item-frontmatter.schema.yaml#/$defs/ItemType"
|
|
51
|
+
- enum: ["", "-", "_TODO_"]
|
|
36
52
|
type: object
|
|
37
53
|
additionalProperties: false
|
|
38
54
|
required:
|
|
@@ -48,6 +64,7 @@ $defs:
|
|
|
48
64
|
- title
|
|
49
65
|
- description
|
|
50
66
|
- type
|
|
67
|
+
- track
|
|
51
68
|
- priority
|
|
52
69
|
- difficulty
|
|
53
70
|
- owner
|
|
@@ -59,7 +76,10 @@ $defs:
|
|
|
59
76
|
- approach
|
|
60
77
|
- targets
|
|
61
78
|
- sources
|
|
79
|
+
- target_path
|
|
80
|
+
- target_rulebook
|
|
62
81
|
- derived_from
|
|
82
|
+
- depends_on
|
|
63
83
|
- autopilot
|
|
64
84
|
from:
|
|
65
85
|
type: string
|
|
@@ -85,6 +85,40 @@ properties:
|
|
|
85
85
|
- recipe-authoring
|
|
86
86
|
- sample-authoring
|
|
87
87
|
- template-authoring
|
|
88
|
+
- if:
|
|
89
|
+
anyOf:
|
|
90
|
+
- required: [target_path]
|
|
91
|
+
properties:
|
|
92
|
+
target_path: true
|
|
93
|
+
- required: [target_rulebook]
|
|
94
|
+
properties:
|
|
95
|
+
target_rulebook: true
|
|
96
|
+
then:
|
|
97
|
+
required: [approach]
|
|
98
|
+
properties:
|
|
99
|
+
approach:
|
|
100
|
+
enum:
|
|
101
|
+
[
|
|
102
|
+
fully-guided,
|
|
103
|
+
recipe-guided,
|
|
104
|
+
freeform,
|
|
105
|
+
retrofit,
|
|
106
|
+
bootstrap,
|
|
107
|
+
finalize,
|
|
108
|
+
bootstrap-finalize,
|
|
109
|
+
]
|
|
110
|
+
- if:
|
|
111
|
+
required: [item_type]
|
|
112
|
+
properties:
|
|
113
|
+
item_type:
|
|
114
|
+
const: epic
|
|
115
|
+
then:
|
|
116
|
+
required: [track]
|
|
117
|
+
properties:
|
|
118
|
+
track: true
|
|
119
|
+
else:
|
|
120
|
+
properties:
|
|
121
|
+
track: false
|
|
88
122
|
- type: object
|
|
89
123
|
required:
|
|
90
124
|
- rulebook
|
|
@@ -128,6 +162,10 @@ properties:
|
|
|
128
162
|
$ref: "#/$defs/ItemType"
|
|
129
163
|
description: "Classification of the register item (list column: 分類)."
|
|
130
164
|
|
|
165
|
+
track:
|
|
166
|
+
$ref: "#/$defs/Track"
|
|
167
|
+
description: "Track governed by this epic; checked against tml-index.yaml when present."
|
|
168
|
+
|
|
131
169
|
item_status:
|
|
132
170
|
$ref: "#/$defs/ItemStatus"
|
|
133
171
|
description: "Processing status of the item (list column: ステータス)."
|
|
@@ -204,6 +242,19 @@ properties:
|
|
|
204
242
|
same project and <project-id>:PJR-XXXX for an item in another project. Omit the key
|
|
205
243
|
when the item was not derived from another register item.
|
|
206
244
|
|
|
245
|
+
depends_on:
|
|
246
|
+
type: array
|
|
247
|
+
items:
|
|
248
|
+
oneOf:
|
|
249
|
+
- $ref: "#/$defs/LocalRegisterItemRef"
|
|
250
|
+
- $ref: "#/$defs/QualifiedRegisterItemRef"
|
|
251
|
+
minItems: 1
|
|
252
|
+
uniqueItems: true
|
|
253
|
+
description: >
|
|
254
|
+
Predecessor register item IDs. Execution requires every predecessor to be done or
|
|
255
|
+
decided; rejected and deferred do not satisfy a dependency. References use the
|
|
256
|
+
same local or project-qualified syntax as derived_from. Cycles are forbidden.
|
|
257
|
+
|
|
207
258
|
autopilot:
|
|
208
259
|
type: string
|
|
209
260
|
const: approved
|
|
@@ -216,7 +267,8 @@ properties:
|
|
|
216
267
|
description: >
|
|
217
268
|
Execution approach. Authoring approaches use the target as the new kata id and
|
|
218
269
|
sources as read-only exemplars. For compatibility, additional targets are also
|
|
219
|
-
accepted as exemplar sources.
|
|
270
|
+
accepted as exemplar sources. Planning approaches require one domain:<id> or track:<id>
|
|
271
|
+
target. Other approaches require one compatible document id.
|
|
220
272
|
|
|
221
273
|
targets:
|
|
222
274
|
type: array
|
|
@@ -225,14 +277,24 @@ properties:
|
|
|
225
277
|
minLength: 1
|
|
226
278
|
minItems: 1
|
|
227
279
|
description: >
|
|
228
|
-
|
|
229
|
-
used with an approach
|
|
280
|
+
Document IDs or planning units (domain:<id> for catalog-planning, track:<id> for strategy-planning). Deliverable targets
|
|
281
|
+
used with an approach prefer the project catalog; target_path and target_rulebook or existing frontmatter allow catalog-less resolution so that
|
|
230
282
|
not-yet-created deliverables can be selected; kata and standalone
|
|
231
283
|
targets are resolved via the doc index. When present, exec plan
|
|
232
284
|
generation copies these into the plan frontmatter so that target
|
|
233
285
|
coverage validation works for register-originated plans. Omit the
|
|
234
286
|
key when the target documents are unknown or not applicable.
|
|
235
287
|
|
|
288
|
+
target_path:
|
|
289
|
+
type: string
|
|
290
|
+
minLength: 1
|
|
291
|
+
description: Repository-relative deliverable path for catalog-less resolution.
|
|
292
|
+
|
|
293
|
+
target_rulebook:
|
|
294
|
+
type: string
|
|
295
|
+
minLength: 1
|
|
296
|
+
description: Deliverable rulebook id; bootstrap requires a new id under kata_authority.
|
|
297
|
+
|
|
236
298
|
sources:
|
|
237
299
|
type: array
|
|
238
300
|
items:
|
|
@@ -247,10 +309,15 @@ properties:
|
|
|
247
309
|
key when the authoring task has no exemplar.
|
|
248
310
|
|
|
249
311
|
$defs:
|
|
312
|
+
Track:
|
|
313
|
+
type: string
|
|
314
|
+
pattern: "^[a-z0-9][a-z0-9-]*$"
|
|
315
|
+
|
|
250
316
|
ItemType:
|
|
251
317
|
type: string
|
|
252
318
|
enum:
|
|
253
319
|
- todo
|
|
320
|
+
- epic
|
|
254
321
|
- question
|
|
255
322
|
- risk
|
|
256
323
|
- issue
|
|
@@ -305,6 +372,8 @@ $defs:
|
|
|
305
372
|
- recipe-guided
|
|
306
373
|
- freeform
|
|
307
374
|
- bootstrap
|
|
375
|
+
- catalog-planning
|
|
376
|
+
- strategy-planning
|
|
308
377
|
- rulebook-authoring
|
|
309
378
|
- recipe-authoring
|
|
310
379
|
- sample-authoring
|
|
@@ -317,7 +386,7 @@ $defs:
|
|
|
317
386
|
- template-maintenance
|
|
318
387
|
- finalize
|
|
319
388
|
- bootstrap-finalize
|
|
320
|
-
description: "Execution approach shared with src/shared/agent-types.ts."
|
|
389
|
+
description: "Execution approach shared with src/shared/agent-types.ts. catalog-planning and strategy-planning are register-only."
|
|
321
390
|
|
|
322
391
|
Date:
|
|
323
392
|
type: string
|
|
@@ -11,11 +11,16 @@ properties:
|
|
|
11
11
|
allOf:
|
|
12
12
|
- $ref: "./common-frontmatter.schema.yaml"
|
|
13
13
|
- type: object
|
|
14
|
+
required:
|
|
15
|
+
- deliverable_type
|
|
14
16
|
properties:
|
|
15
17
|
type:
|
|
16
18
|
type: string
|
|
17
19
|
const: rulebook
|
|
18
20
|
description: "ドキュメント種別(rulebook 固定)"
|
|
21
|
+
deliverable_type:
|
|
22
|
+
$ref: "./deliverable-frontmatter.schema.yaml#/$defs/deliverableType"
|
|
23
|
+
description: "扱う成果物の type。Markdown 成果物・sample・生成物 Frontmatter 雛形との照合の正本。"
|
|
19
24
|
target_format:
|
|
20
25
|
type: string
|
|
21
26
|
enum:
|
|
@@ -148,6 +148,11 @@ $defs:
|
|
|
148
148
|
integration_branch:
|
|
149
149
|
description: Branch exec integrates into. Omit to use the repository's current branch.
|
|
150
150
|
$ref: "#/$defs/NonEmptyString"
|
|
151
|
+
integration_strategy:
|
|
152
|
+
description: Local merge commit (default), or retain the exec branch for product-side PR review.
|
|
153
|
+
type: string
|
|
154
|
+
enum: [merge, branch-only]
|
|
155
|
+
default: merge
|
|
151
156
|
setup:
|
|
152
157
|
description: Whether exec installs dependencies and builds in the repository worktree.
|
|
153
158
|
type: object
|
|
@@ -166,9 +171,22 @@ $defs:
|
|
|
166
171
|
type: string
|
|
167
172
|
parent_validations:
|
|
168
173
|
description: >-
|
|
169
|
-
Parent-runner validations appended, in order,
|
|
170
|
-
|
|
171
|
-
targets project
|
|
174
|
+
Parent-runner validations appended, in order, after parent_validations_exclude removes
|
|
175
|
+
matching entries from pipeline.parent_validations in this project's exec_defaults file.
|
|
176
|
+
A plain ID targets the project repository; { id, repo } targets project or a product
|
|
177
|
+
repository declared by this project. Duplicate ID/repository pairs in the effective list
|
|
178
|
+
are rejected before agent launch.
|
|
179
|
+
type: array
|
|
180
|
+
uniqueItems: true
|
|
181
|
+
items:
|
|
182
|
+
$ref: "#/$defs/ParentValidation"
|
|
183
|
+
parent_validations_exclude:
|
|
184
|
+
description: >-
|
|
185
|
+
Remove these ID/repository pairs from shared pipeline.parent_validations before appending
|
|
186
|
+
this project's parent_validations. Omitted or [] preserves the shared list. A plain ID
|
|
187
|
+
matches only the project repository, equivalently { id, repo: project }. Every exclusion
|
|
188
|
+
must exist in the shared list; missing entries and duplicate pairs are configuration
|
|
189
|
+
errors checked by the CLI before agent launch. Other projects are unaffected.
|
|
172
190
|
type: array
|
|
173
191
|
uniqueItems: true
|
|
174
192
|
items:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "specdojo",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.5.0",
|
|
4
4
|
"description": "A dojo for Spec-Dō, the way of specification: decide with a register, write specs and designs with kata, and keep sharpening them with AI.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "naoji3x",
|
|
@@ -90,7 +90,7 @@
|
|
|
90
90
|
"docs:generate": "node --import tsx src/specdojo.ts build",
|
|
91
91
|
"docs:dev": "npm run docs:generate && npm --prefix packages/docs-site run docs:dev",
|
|
92
92
|
"docs:build:mermaid": "npm --prefix packages/docs-site run docs:build:mermaid",
|
|
93
|
-
"docs:rebuild:mermaid": "rm -f
|
|
93
|
+
"docs:rebuild:mermaid": "rm -f .vitepress/mermaid/*.svg && npm run docs:build:mermaid",
|
|
94
94
|
"docs:build": "npm run docs:generate && npm --prefix packages/docs-site run docs:build",
|
|
95
95
|
"lint:fm": "node packages/docs-lint/bin/specdojo-docs-lint.js remark \"docs/**/*.{md,mdx}\" --quiet --frail",
|
|
96
96
|
"validate:schema:job-run": "node packages/docs-lint/bin/specdojo-docs-lint.js yaml-schema --schema docs/specdojo/schemas/v1/job-run.schema.yaml --data \"docs/ja/**/execution/jobs/runs/*.json\" --allow-empty",
|
|
@@ -85,15 +85,16 @@ catalog へ進む段階になったら、`.specdojo/specdojo.config.json` へ `c
|
|
|
85
85
|
|
|
86
86
|
type は次のように使い分ける。
|
|
87
87
|
|
|
88
|
-
| type | 用途
|
|
89
|
-
| ---------------- |
|
|
90
|
-
| `issue` | 解決すべき問題。原因調査を伴う
|
|
91
|
-
| `decision` | 選択肢から方針を決める
|
|
92
|
-
| `todo` | 実施する作業
|
|
93
|
-
| `question` | 判断を保留し、後で決める
|
|
94
|
-
| `risk` | 将来の不確実性
|
|
95
|
-
| `change-request` | 合意済み範囲の変更要求
|
|
96
|
-
| `note` | 記録として残す観測・分析
|
|
88
|
+
| type | 用途 | 終端状態 |
|
|
89
|
+
| ---------------- | ---------------------------------- | --------- |
|
|
90
|
+
| `issue` | 解決すべき問題。原因調査を伴う | `done` |
|
|
91
|
+
| `decision` | 選択肢から方針を決める | `decided` |
|
|
92
|
+
| `todo` | 実施する作業 | `done` |
|
|
93
|
+
| `question` | 判断を保留し、後で決める | `decided` |
|
|
94
|
+
| `risk` | 将来の不確実性 | `done` |
|
|
95
|
+
| `change-request` | 合意済み範囲の変更要求 | `done` |
|
|
96
|
+
| `note` | 記録として残す観測・分析 | なし |
|
|
97
|
+
| `epic` | track ごとの仕事の着手と完了の管理 | `done` |
|
|
97
98
|
|
|
98
99
|
起票では `--title` と `--description` を具体的に書く。`--description` は一覧へ出るため、後から見て内容が分かる文にする。`--topic` を省くとタイトルの英数字の部分から導出される。タイトルが日本語の場合は、内容を表す英語の `--topic`(小文字・ハイフン区切り。例: `payment-scope`)を渡す。
|
|
99
100
|
|
|
@@ -123,6 +124,10 @@ npx specdojo register close --project <project-id> --id <PJR-XXXX> \
|
|
|
123
124
|
|
|
124
125
|
`decision` と `question` は `--status decided` を付ける。close の前に個票の `決定内容` / `承認` を埋める。
|
|
125
126
|
|
|
127
|
+
`epic` は `--track <track>` で担う track を指定して起票し、具体的な作業は `--from <epic-id>` を付けた子 todo に分解する。epic 自体は `exec run --register` で実行せず、夜間の実行でも飛ばされる。子項目の状態は `register build` が生成する epic ごとのビューで確かめ、子項目と schedule を材料に人が close を判断する。
|
|
128
|
+
|
|
129
|
+
順番のある項目は `--depends-on <PJR-XXXX>`(繰り返し指定できる)で先に終わっているべき項目を記録する。起票の由来を表す `--from`(`derived_from`)とは別の意味で、どちらかで他方を兼ねない。先行の項目がすべて `done` / `decided` になるまで、`exec run --register` は止まり、夜間の実行では飛ばされる。状態は自動では `waiting` にならない。外すときは `--depends-on -` を指定する。後続の項目は一覧の `depends_on` 列と `generated/pjr-dependent-items.md` で確かめる。
|
|
130
|
+
|
|
126
131
|
`note` は終端させず、`open` のまま新しい事実・知見を追記する。close / reject / defer の対象にしない。対応や判断が必要になった場合は、目的に合う別の type で起票し、note は参照元として残す(`pjr-rulebook` の type 別の扱い)。
|
|
127
132
|
|
|
128
133
|
## 実践の型(kata)の扱い
|
|
@@ -92,15 +92,16 @@ catalog へ進む段階になったら、`.specdojo/specdojo.config.json` へ `c
|
|
|
92
92
|
|
|
93
93
|
type は次のように使い分ける。
|
|
94
94
|
|
|
95
|
-
| type | 用途
|
|
96
|
-
| ---------------- |
|
|
97
|
-
| `issue` | 解決すべき問題。原因調査を伴う
|
|
98
|
-
| `decision` | 選択肢から方針を決める
|
|
99
|
-
| `todo` | 実施する作業
|
|
100
|
-
| `question` | 判断を保留し、後で決める
|
|
101
|
-
| `risk` | 将来の不確実性
|
|
102
|
-
| `change-request` | 合意済み範囲の変更要求
|
|
103
|
-
| `note` | 記録として残す観測・分析
|
|
95
|
+
| type | 用途 | 終端状態 |
|
|
96
|
+
| ---------------- | ---------------------------------- | --------- |
|
|
97
|
+
| `issue` | 解決すべき問題。原因調査を伴う | `done` |
|
|
98
|
+
| `decision` | 選択肢から方針を決める | `decided` |
|
|
99
|
+
| `todo` | 実施する作業 | `done` |
|
|
100
|
+
| `question` | 判断を保留し、後で決める | `decided` |
|
|
101
|
+
| `risk` | 将来の不確実性 | `done` |
|
|
102
|
+
| `change-request` | 合意済み範囲の変更要求 | `done` |
|
|
103
|
+
| `note` | 記録として残す観測・分析 | なし |
|
|
104
|
+
| `epic` | track ごとの仕事の着手と完了の管理 | `done` |
|
|
104
105
|
|
|
105
106
|
起票では `--title` と `--description` を具体的に書く。`--description` は一覧へ出るため、後から見て内容が分かる文にする。`--topic` を省くとタイトルの英数字の部分から導出される。タイトルが日本語の場合は、内容を表す英語の `--topic`(小文字・ハイフン区切り。例: `payment-scope`)を渡す。
|
|
106
107
|
|
|
@@ -130,6 +131,10 @@ npx specdojo register close --project <project-id> --id <PJR-XXXX> \
|
|
|
130
131
|
|
|
131
132
|
`decision` と `question` は `--status decided` を付ける。close の前に個票の `決定内容` / `承認` を埋める。
|
|
132
133
|
|
|
134
|
+
`epic` は `--track <track>` で担う track を指定して起票し、具体的な作業は `--from <epic-id>` を付けた子 todo に分解する。epic 自体は `exec run --register` で実行せず、夜間の実行でも飛ばされる。子項目の状態は `register build` が生成する epic ごとのビューで確かめ、子項目と schedule を材料に人が close を判断する。
|
|
135
|
+
|
|
136
|
+
順番のある項目は `--depends-on <PJR-XXXX>`(繰り返し指定できる)で先に終わっているべき項目を記録する。起票の由来を表す `--from`(`derived_from`)とは別の意味で、どちらかで他方を兼ねない。先行の項目がすべて `done` / `decided` になるまで、`exec run --register` は止まり、夜間の実行では飛ばされる。状態は自動では `waiting` にならない。外すときは `--depends-on -` を指定する。後続の項目は一覧の `depends_on` 列と `generated/pjr-dependent-items.md` で確かめる。
|
|
137
|
+
|
|
133
138
|
`note` は終端させず、`open` のまま新しい事実・知見を追記する。close / reject / defer の対象にしない。対応や判断が必要になった場合は、目的に合う別の type で起票し、note は参照元として残す(`pjr-rulebook` の type 別の扱い)。
|
|
134
139
|
|
|
135
140
|
## 実践の型(kata)の扱い
|
|
@@ -92,15 +92,16 @@ catalog へ進む段階になったら、`.specdojo/specdojo.config.json` へ `c
|
|
|
92
92
|
|
|
93
93
|
type は次のように使い分ける。
|
|
94
94
|
|
|
95
|
-
| type | 用途
|
|
96
|
-
| ---------------- |
|
|
97
|
-
| `issue` | 解決すべき問題。原因調査を伴う
|
|
98
|
-
| `decision` | 選択肢から方針を決める
|
|
99
|
-
| `todo` | 実施する作業
|
|
100
|
-
| `question` | 判断を保留し、後で決める
|
|
101
|
-
| `risk` | 将来の不確実性
|
|
102
|
-
| `change-request` | 合意済み範囲の変更要求
|
|
103
|
-
| `note` | 記録として残す観測・分析
|
|
95
|
+
| type | 用途 | 終端状態 |
|
|
96
|
+
| ---------------- | ---------------------------------- | --------- |
|
|
97
|
+
| `issue` | 解決すべき問題。原因調査を伴う | `done` |
|
|
98
|
+
| `decision` | 選択肢から方針を決める | `decided` |
|
|
99
|
+
| `todo` | 実施する作業 | `done` |
|
|
100
|
+
| `question` | 判断を保留し、後で決める | `decided` |
|
|
101
|
+
| `risk` | 将来の不確実性 | `done` |
|
|
102
|
+
| `change-request` | 合意済み範囲の変更要求 | `done` |
|
|
103
|
+
| `note` | 記録として残す観測・分析 | なし |
|
|
104
|
+
| `epic` | track ごとの仕事の着手と完了の管理 | `done` |
|
|
104
105
|
|
|
105
106
|
起票では `--title` と `--description` を具体的に書く。`--description` は一覧へ出るため、後から見て内容が分かる文にする。`--topic` を省くとタイトルの英数字の部分から導出される。タイトルが日本語の場合は、内容を表す英語の `--topic`(小文字・ハイフン区切り。例: `payment-scope`)を渡す。
|
|
106
107
|
|
|
@@ -130,6 +131,10 @@ npx specdojo register close --project <project-id> --id <PJR-XXXX> \
|
|
|
130
131
|
|
|
131
132
|
`decision` と `question` は `--status decided` を付ける。close の前に個票の `決定内容` / `承認` を埋める。
|
|
132
133
|
|
|
134
|
+
`epic` は `--track <track>` で担う track を指定して起票し、具体的な作業は `--from <epic-id>` を付けた子 todo に分解する。epic 自体は `exec run --register` で実行せず、夜間の実行でも飛ばされる。子項目の状態は `register build` が生成する epic ごとのビューで確かめ、子項目と schedule を材料に人が close を判断する。
|
|
135
|
+
|
|
136
|
+
順番のある項目は `--depends-on <PJR-XXXX>`(繰り返し指定できる)で先に終わっているべき項目を記録する。起票の由来を表す `--from`(`derived_from`)とは別の意味で、どちらかで他方を兼ねない。先行の項目がすべて `done` / `decided` になるまで、`exec run --register` は止まり、夜間の実行では飛ばされる。状態は自動では `waiting` にならない。外すときは `--depends-on -` を指定する。後続の項目は一覧の `depends_on` 列と `generated/pjr-dependent-items.md` で確かめる。
|
|
137
|
+
|
|
133
138
|
`note` は終端させず、`open` のまま新しい事実・知見を追記する。close / reject / defer の対象にしない。対応や判断が必要になった場合は、目的に合う別の type で起票し、note は参照元として残す(`pjr-rulebook` の type 別の扱い)。
|
|
134
139
|
|
|
135
140
|
## 実践の型(kata)の扱い
|
|
@@ -85,15 +85,16 @@ catalog へ進む段階になったら、`.specdojo/specdojo.config.json` へ `c
|
|
|
85
85
|
|
|
86
86
|
type は次のように使い分ける。
|
|
87
87
|
|
|
88
|
-
| type | 用途
|
|
89
|
-
| ---------------- |
|
|
90
|
-
| `issue` | 解決すべき問題。原因調査を伴う
|
|
91
|
-
| `decision` | 選択肢から方針を決める
|
|
92
|
-
| `todo` | 実施する作業
|
|
93
|
-
| `question` | 判断を保留し、後で決める
|
|
94
|
-
| `risk` | 将来の不確実性
|
|
95
|
-
| `change-request` | 合意済み範囲の変更要求
|
|
96
|
-
| `note` | 記録として残す観測・分析
|
|
88
|
+
| type | 用途 | 終端状態 |
|
|
89
|
+
| ---------------- | ---------------------------------- | --------- |
|
|
90
|
+
| `issue` | 解決すべき問題。原因調査を伴う | `done` |
|
|
91
|
+
| `decision` | 選択肢から方針を決める | `decided` |
|
|
92
|
+
| `todo` | 実施する作業 | `done` |
|
|
93
|
+
| `question` | 判断を保留し、後で決める | `decided` |
|
|
94
|
+
| `risk` | 将来の不確実性 | `done` |
|
|
95
|
+
| `change-request` | 合意済み範囲の変更要求 | `done` |
|
|
96
|
+
| `note` | 記録として残す観測・分析 | なし |
|
|
97
|
+
| `epic` | track ごとの仕事の着手と完了の管理 | `done` |
|
|
97
98
|
|
|
98
99
|
起票では `--title` と `--description` を具体的に書く。`--description` は一覧へ出るため、後から見て内容が分かる文にする。`--topic` を省くとタイトルの英数字の部分から導出される。タイトルが日本語の場合は、内容を表す英語の `--topic`(小文字・ハイフン区切り。例: `payment-scope`)を渡す。
|
|
99
100
|
|
|
@@ -123,6 +124,10 @@ npx specdojo register close --project <project-id> --id <PJR-XXXX> \
|
|
|
123
124
|
|
|
124
125
|
`decision` と `question` は `--status decided` を付ける。close の前に個票の `決定内容` / `承認` を埋める。
|
|
125
126
|
|
|
127
|
+
`epic` は `--track <track>` で担う track を指定して起票し、具体的な作業は `--from <epic-id>` を付けた子 todo に分解する。epic 自体は `exec run --register` で実行せず、夜間の実行でも飛ばされる。子項目の状態は `register build` が生成する epic ごとのビューで確かめ、子項目と schedule を材料に人が close を判断する。
|
|
128
|
+
|
|
129
|
+
順番のある項目は `--depends-on <PJR-XXXX>`(繰り返し指定できる)で先に終わっているべき項目を記録する。起票の由来を表す `--from`(`derived_from`)とは別の意味で、どちらかで他方を兼ねない。先行の項目がすべて `done` / `decided` になるまで、`exec run --register` は止まり、夜間の実行では飛ばされる。状態は自動では `waiting` にならない。外すときは `--depends-on -` を指定する。後続の項目は一覧の `depends_on` 列と `generated/pjr-dependent-items.md` で確かめる。
|
|
130
|
+
|
|
126
131
|
`note` は終端させず、`open` のまま新しい事実・知見を追記する。close / reject / defer の対象にしない。対応や判断が必要になった場合は、目的に合う別の type で起票し、note は参照元として残す(`pjr-rulebook` の type 別の扱い)。
|
|
127
132
|
|
|
128
133
|
## 実践の型(kata)の扱い
|
|
@@ -33,7 +33,8 @@ specdojo config scaffold --provider copilot
|
|
|
33
33
|
2. `.specdojo/copilot/agent-members-snippet.yaml` の member 定義をリポジトリ共通の `.specdojo/agent-members.yaml` の `members` へコピーし、使う場合は `disabled: false` にする。agent は project ごとの `pm-members.yaml` へ書かない。
|
|
34
34
|
3. `copilot login` で認証する(premium request の課金が発生する)。
|
|
35
35
|
4. `npm run orch:copilot` でオーケストレーターを起動できることを確認する。
|
|
36
|
-
5.
|
|
36
|
+
5. VS Code から使う場合は、Copilot Chat を開き、agent の選択肢から `specdojo-orchestrator` を選ぶ(`.github/agents/specdojo-orchestrator.md` が読み込まれます)。
|
|
37
|
+
6. 最初のタスクで permission ログを確認し、`shell(...)` パターンのマッチ粒度が不足していれば `--allow-tool` を追記する。
|
|
37
38
|
|
|
38
39
|
## 4. カスタマイズ
|
|
39
40
|
|
|
@@ -5,6 +5,7 @@
|
|
|
5
5
|
"init": true,
|
|
6
6
|
"workspaceMount": "source=${localWorkspaceFolder}/..,target=/workspaces/__SPECDOJO_WORKSPACE_NAME__,type=bind,consistency=cached",
|
|
7
7
|
"workspaceFolder": "/workspaces/__SPECDOJO_WORKSPACE_NAME__/${localWorkspaceFolderBasename}",
|
|
8
|
+
"shutdownAction": "none",
|
|
8
9
|
"features": {
|
|
9
10
|
"ghcr.io/devcontainers/features/common-utils:2": {
|
|
10
11
|
"installZsh": false,
|