@llipe.com/dev-tasks 0.11.0 → 0.16.1
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/.claude/agents/developer.md +105 -43
- package/.claude/agents/github-ops.md +48 -4
- package/.claude/agents/housekeeping.md +44 -7
- package/.claude/agents/qa-engineer.md +24 -11
- package/.claude/agents/researcher.md +26 -6
- package/.claude/agents/technical-writer.md +61 -6
- package/.claude/agents/ux-engineer.md +1 -0
- package/.claude/agents/verifier.md +48 -6
- package/.claude/commands/developer.md +2 -266
- package/.claude/commands/infra-engineer.md +92 -0
- package/.claude/commands/planner.md +44 -23
- package/.claude/commands/product-engineer.md +21 -9
- package/.claude/commands/researcher.md +4 -5
- package/.claude/commands/technical-writer.md +1 -1
- package/.claude/hooks/branch-guard.sh +30 -0
- package/.claude/hooks/git-guard.sh +483 -22
- package/.claude/skills/activity-codebase-research/SKILL.md +4 -11
- package/.claude/skills/activity-generate-spec/SKILL.md +34 -10
- package/.claude/skills/activity-grill/SKILL.md +150 -0
- package/.claude/skills/activity-init/SKILL.md +121 -71
- package/.claude/skills/activity-refine/SKILL.md +75 -15
- package/.claude/skills/activity-test-standards/SKILL.md +25 -0
- package/.claude/skills/aws-ops/SKILL.md +155 -0
- package/.claude/skills/deploy-ops/SKILL.md +121 -0
- package/.claude/skills/fly-ops/SKILL.md +138 -0
- package/.claude/skills/git-ops/SKILL.md +27 -7
- package/.claude/skills/implement/SKILL.md +49 -4
- package/.claude/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.claude/skills/memo-cli-usage/SKILL.md +66 -13
- package/.claude/skills/plan/SKILL.md +43 -1
- package/.claude/skills/supabase-ops/SKILL.md +109 -0
- package/.github/agents/developer.agent.md +70 -19
- package/.github/agents/github-ops.agent.md +46 -4
- package/.github/agents/housekeeping.agent.md +43 -7
- package/.github/agents/infra-engineer.agent.md +139 -0
- package/.github/agents/planner.agent.md +25 -4
- package/.github/agents/product-engineer.agent.md +21 -9
- package/.github/agents/qa-engineer.agent.md +23 -11
- package/.github/agents/researcher.agent.md +25 -6
- package/.github/agents/technical-writer.agent.md +60 -6
- package/.github/agents/verifier.agent.md +46 -5
- package/.github/instructions/implement.instructions.md +49 -4
- package/.github/instructions/plan.instructions.md +43 -1
- package/.github/prompts/infra-engineer.prompt.md +12 -0
- package/.github/prompts/product-engineer-init.prompt.md +5 -6
- package/.github/prompts/researcher.prompt.md +4 -5
- package/.github/prompts/technical-writer.prompt.md +1 -1
- package/.github/skills/activity-codebase-research/SKILL.md +4 -16
- package/.github/skills/activity-generate-spec/SKILL.md +34 -10
- package/.github/skills/activity-grill/SKILL.md +145 -0
- package/.github/skills/activity-init/SKILL.md +120 -70
- package/.github/skills/activity-refine/SKILL.md +75 -15
- package/.github/skills/activity-test-standards/SKILL.md +25 -0
- package/.github/skills/aws-ops/SKILL.md +150 -0
- package/.github/skills/deploy-ops/SKILL.md +116 -0
- package/.github/skills/fly-ops/SKILL.md +133 -0
- package/.github/skills/git-ops/SKILL.md +27 -7
- package/.github/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.github/skills/memo-cli-usage/SKILL.md +66 -13
- package/.github/skills/supabase-ops/SKILL.md +104 -0
- package/.kiro/agents/developer.md +71 -20
- package/.kiro/agents/github-ops.md +46 -4
- package/.kiro/agents/housekeeping.md +44 -8
- package/.kiro/agents/infra-engineer.md +102 -0
- package/.kiro/agents/planner.md +33 -15
- package/.kiro/agents/product-engineer.md +24 -12
- package/.kiro/agents/qa-engineer.md +24 -12
- package/.kiro/agents/researcher.md +26 -7
- package/.kiro/agents/technical-writer.md +63 -9
- package/.kiro/agents/verifier.md +47 -6
- package/.kiro/skills/activity-codebase-research/SKILL.md +4 -11
- package/.kiro/skills/activity-generate-spec/SKILL.md +34 -10
- package/.kiro/skills/activity-grill/SKILL.md +150 -0
- package/.kiro/skills/activity-init/SKILL.md +121 -71
- package/.kiro/skills/activity-refine/SKILL.md +75 -15
- package/.kiro/skills/activity-test-standards/SKILL.md +25 -0
- package/.kiro/skills/aws-ops/SKILL.md +155 -0
- package/.kiro/skills/deploy-ops/SKILL.md +121 -0
- package/.kiro/skills/fly-ops/SKILL.md +138 -0
- package/.kiro/skills/git-ops/SKILL.md +27 -7
- package/.kiro/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.kiro/skills/memo-cli-usage/SKILL.md +66 -13
- package/.kiro/skills/supabase-ops/SKILL.md +109 -0
- package/.kiro/steering/implement.md +49 -4
- package/.kiro/steering/plan.md +43 -1
- package/AGENTS.md +60 -109
- package/AGENTS.md.template +124 -0
- package/CHANGELOG.md +163 -0
- package/CLAUDE.md +23 -18
- package/CLAUDE.md.template +103 -0
- package/README.md +168 -146
- package/TESTING.md +84 -148
- package/bundle-manifest.json +43 -2
- package/dist/bin/dev-tasks.js +65 -3
- package/dist/bin/dev-tasks.js.map +1 -1
- package/dist/{adapters/cli → bin}/parse-args.d.ts +2 -6
- package/dist/bin/parse-args.d.ts.map +1 -0
- package/dist/{adapters/cli → bin}/parse-args.js +2 -18
- package/dist/bin/parse-args.js.map +1 -0
- package/dist/core/checks/decision-log-format.d.ts +44 -0
- package/dist/core/checks/decision-log-format.d.ts.map +1 -0
- package/dist/core/checks/decision-log-format.js +171 -0
- package/dist/core/checks/decision-log-format.js.map +1 -0
- package/dist/core/checks/docs-structure.d.ts +82 -0
- package/dist/core/checks/docs-structure.d.ts.map +1 -0
- package/dist/core/checks/docs-structure.js +285 -0
- package/dist/core/checks/docs-structure.js.map +1 -0
- package/dist/core/checks/glossary.d.ts +178 -0
- package/dist/core/checks/glossary.d.ts.map +1 -0
- package/dist/core/checks/glossary.js +651 -0
- package/dist/core/checks/glossary.js.map +1 -0
- package/dist/core/checks/index.d.ts +19 -0
- package/dist/core/checks/index.d.ts.map +1 -0
- package/dist/core/checks/index.js +16 -0
- package/dist/core/checks/index.js.map +1 -0
- package/dist/core/checks/run.d.ts +22 -0
- package/dist/core/checks/run.d.ts.map +1 -0
- package/dist/core/checks/run.js +51 -0
- package/dist/core/checks/run.js.map +1 -0
- package/dist/core/distribution/doctor.d.ts +46 -1
- package/dist/core/distribution/doctor.d.ts.map +1 -1
- package/dist/core/distribution/doctor.js +161 -2
- package/dist/core/distribution/doctor.js.map +1 -1
- package/dist/core/distribution/index.d.ts +9 -3
- package/dist/core/distribution/index.d.ts.map +1 -1
- package/dist/core/distribution/index.js +5 -2
- package/dist/core/distribution/index.js.map +1 -1
- package/dist/core/distribution/install-if-absent.d.ts +46 -0
- package/dist/core/distribution/install-if-absent.d.ts.map +1 -0
- package/dist/core/distribution/install-if-absent.js +81 -0
- package/dist/core/distribution/install-if-absent.js.map +1 -0
- package/dist/core/distribution/install.d.ts.map +1 -1
- package/dist/core/distribution/install.js +5 -0
- package/dist/core/distribution/install.js.map +1 -1
- package/dist/core/distribution/migrate-docs.d.ts +64 -0
- package/dist/core/distribution/migrate-docs.d.ts.map +1 -0
- package/dist/core/distribution/migrate-docs.js +139 -0
- package/dist/core/distribution/migrate-docs.js.map +1 -0
- package/dist/core/distribution/profiles.d.ts +49 -0
- package/dist/core/distribution/profiles.d.ts.map +1 -1
- package/dist/core/distribution/profiles.js +45 -0
- package/dist/core/distribution/profiles.js.map +1 -1
- package/dist/core/distribution/update.d.ts +14 -0
- package/dist/core/distribution/update.d.ts.map +1 -1
- package/dist/core/distribution/update.js +77 -3
- package/dist/core/distribution/update.js.map +1 -1
- package/dist/core/distribution/workspace.d.ts +84 -0
- package/dist/core/distribution/workspace.d.ts.map +1 -0
- package/dist/core/distribution/workspace.js +276 -0
- package/dist/core/distribution/workspace.js.map +1 -0
- package/dist/core/exit-codes.d.ts +15 -35
- package/dist/core/exit-codes.d.ts.map +1 -1
- package/dist/core/exit-codes.js +15 -36
- package/dist/core/exit-codes.js.map +1 -1
- package/dist/core/index.d.ts +1 -6
- package/dist/core/index.d.ts.map +1 -1
- package/dist/core/index.js +1 -7
- package/dist/core/index.js.map +1 -1
- package/package.json +17 -32
- package/templates/claude/settings.json +48 -0
- package/templates/domain/ubiquitous-language.md +28 -0
- package/templates/infra/environments.yaml +16 -0
- package/templates/infra/redaction-patterns.txt +47 -0
- package/templates/runbooks/README.md +14 -0
- package/templates/runbooks/runbook-template.md +40 -0
- package/templates/scripts/deploy-status.sh +89 -0
- package/templates/scripts/deploy-verify.sh +85 -0
- package/templates/scripts/deploy.sh +284 -0
- package/templates/scripts/release.sh +170 -0
- package/templates/scripts/rollback.sh +109 -0
- package/templates/workflows/deploy-dev.yml +66 -0
- package/templates/workflows/deploy-prod.yml +66 -0
- package/templates/workflows/rollback.yml +77 -0
- package/.claude/skills/activity-contract-validation/SKILL.md +0 -167
- package/.github/skills/activity-contract-validation/SKILL.md +0 -167
- package/.kiro/skills/activity-contract-validation/SKILL.md +0 -167
- package/dist/adapters/cli/catalog-build.d.ts +0 -30
- package/dist/adapters/cli/catalog-build.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-build.js +0 -73
- package/dist/adapters/cli/catalog-build.js.map +0 -1
- package/dist/adapters/cli/catalog-query.d.ts +0 -13
- package/dist/adapters/cli/catalog-query.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-query.js +0 -329
- package/dist/adapters/cli/catalog-query.js.map +0 -1
- package/dist/adapters/cli/catalog-scaffold.d.ts +0 -24
- package/dist/adapters/cli/catalog-scaffold.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-scaffold.js +0 -46
- package/dist/adapters/cli/catalog-scaffold.js.map +0 -1
- package/dist/adapters/cli/catalog-validate.d.ts +0 -35
- package/dist/adapters/cli/catalog-validate.d.ts.map +0 -1
- package/dist/adapters/cli/catalog-validate.js +0 -122
- package/dist/adapters/cli/catalog-validate.js.map +0 -1
- package/dist/adapters/cli/ctx-assemble.d.ts +0 -19
- package/dist/adapters/cli/ctx-assemble.d.ts.map +0 -1
- package/dist/adapters/cli/ctx-assemble.js +0 -293
- package/dist/adapters/cli/ctx-assemble.js.map +0 -1
- package/dist/adapters/cli/ctx-fetch.d.ts +0 -49
- package/dist/adapters/cli/ctx-fetch.d.ts.map +0 -1
- package/dist/adapters/cli/ctx-fetch.js +0 -267
- package/dist/adapters/cli/ctx-fetch.js.map +0 -1
- package/dist/adapters/cli/extract-all.d.ts +0 -31
- package/dist/adapters/cli/extract-all.d.ts.map +0 -1
- package/dist/adapters/cli/extract-all.js +0 -374
- package/dist/adapters/cli/extract-all.js.map +0 -1
- package/dist/adapters/cli/extract-asyncapi.d.ts +0 -26
- package/dist/adapters/cli/extract-asyncapi.d.ts.map +0 -1
- package/dist/adapters/cli/extract-asyncapi.js +0 -142
- package/dist/adapters/cli/extract-asyncapi.js.map +0 -1
- package/dist/adapters/cli/extract-component.d.ts +0 -24
- package/dist/adapters/cli/extract-component.d.ts.map +0 -1
- package/dist/adapters/cli/extract-component.js +0 -198
- package/dist/adapters/cli/extract-component.js.map +0 -1
- package/dist/adapters/cli/extract-detect.d.ts +0 -19
- package/dist/adapters/cli/extract-detect.d.ts.map +0 -1
- package/dist/adapters/cli/extract-detect.js +0 -98
- package/dist/adapters/cli/extract-detect.js.map +0 -1
- package/dist/adapters/cli/extract-openapi.d.ts +0 -29
- package/dist/adapters/cli/extract-openapi.d.ts.map +0 -1
- package/dist/adapters/cli/extract-openapi.js +0 -111
- package/dist/adapters/cli/extract-openapi.js.map +0 -1
- package/dist/adapters/cli/extract-schema.d.ts +0 -15
- package/dist/adapters/cli/extract-schema.d.ts.map +0 -1
- package/dist/adapters/cli/extract-schema.js +0 -39
- package/dist/adapters/cli/extract-schema.js.map +0 -1
- package/dist/adapters/cli/index.d.ts +0 -6
- package/dist/adapters/cli/index.d.ts.map +0 -1
- package/dist/adapters/cli/index.js +0 -5
- package/dist/adapters/cli/index.js.map +0 -1
- package/dist/adapters/cli/init.d.ts +0 -37
- package/dist/adapters/cli/init.d.ts.map +0 -1
- package/dist/adapters/cli/init.js +0 -336
- package/dist/adapters/cli/init.js.map +0 -1
- package/dist/adapters/cli/parse-args.d.ts.map +0 -1
- package/dist/adapters/cli/parse-args.js.map +0 -1
- package/dist/adapters/cli/scope-gate.d.ts +0 -25
- package/dist/adapters/cli/scope-gate.d.ts.map +0 -1
- package/dist/adapters/cli/scope-gate.js +0 -157
- package/dist/adapters/cli/scope-gate.js.map +0 -1
- package/dist/adapters/cli/scope.d.ts +0 -26
- package/dist/adapters/cli/scope.d.ts.map +0 -1
- package/dist/adapters/cli/scope.js +0 -172
- package/dist/adapters/cli/scope.js.map +0 -1
- package/dist/adapters/cli/validate-component.d.ts +0 -24
- package/dist/adapters/cli/validate-component.d.ts.map +0 -1
- package/dist/adapters/cli/validate-component.js +0 -62
- package/dist/adapters/cli/validate-component.js.map +0 -1
- package/dist/adapters/cli/verify-contract-diff.d.ts +0 -21
- package/dist/adapters/cli/verify-contract-diff.d.ts.map +0 -1
- package/dist/adapters/cli/verify-contract-diff.js +0 -69
- package/dist/adapters/cli/verify-contract-diff.js.map +0 -1
- package/dist/adapters/cli/verify-drift.d.ts +0 -24
- package/dist/adapters/cli/verify-drift.d.ts.map +0 -1
- package/dist/adapters/cli/verify-drift.js +0 -103
- package/dist/adapters/cli/verify-drift.js.map +0 -1
- package/dist/adapters/cli/verify-impact.d.ts +0 -23
- package/dist/adapters/cli/verify-impact.d.ts.map +0 -1
- package/dist/adapters/cli/verify-impact.js +0 -119
- package/dist/adapters/cli/verify-impact.js.map +0 -1
- package/dist/adapters/mcp/index.d.ts +0 -5
- package/dist/adapters/mcp/index.d.ts.map +0 -1
- package/dist/adapters/mcp/index.js +0 -2
- package/dist/adapters/mcp/index.js.map +0 -1
- package/dist/bin/dt.d.ts +0 -7
- package/dist/bin/dt.d.ts.map +0 -1
- package/dist/bin/dt.js +0 -647
- package/dist/bin/dt.js.map +0 -1
- package/dist/core/catalog/build.d.ts +0 -143
- package/dist/core/catalog/build.d.ts.map +0 -1
- package/dist/core/catalog/build.js +0 -475
- package/dist/core/catalog/build.js.map +0 -1
- package/dist/core/catalog/checks/index.d.ts +0 -18
- package/dist/core/catalog/checks/index.d.ts.map +0 -1
- package/dist/core/catalog/checks/index.js +0 -18
- package/dist/core/catalog/checks/index.js.map +0 -1
- package/dist/core/catalog/checks/v01-schema.d.ts +0 -17
- package/dist/core/catalog/checks/v01-schema.d.ts.map +0 -1
- package/dist/core/catalog/checks/v01-schema.js +0 -57
- package/dist/core/catalog/checks/v01-schema.js.map +0 -1
- package/dist/core/catalog/checks/v02-v03-identity.d.ts +0 -14
- package/dist/core/catalog/checks/v02-v03-identity.d.ts.map +0 -1
- package/dist/core/catalog/checks/v02-v03-identity.js +0 -60
- package/dist/core/catalog/checks/v02-v03-identity.js.map +0 -1
- package/dist/core/catalog/checks/v04-referential-integrity.d.ts +0 -7
- package/dist/core/catalog/checks/v04-referential-integrity.d.ts.map +0 -1
- package/dist/core/catalog/checks/v04-referential-integrity.js +0 -32
- package/dist/core/catalog/checks/v04-referential-integrity.js.map +0 -1
- package/dist/core/catalog/checks/v05-domain-existence.d.ts +0 -6
- package/dist/core/catalog/checks/v05-domain-existence.d.ts.map +0 -1
- package/dist/core/catalog/checks/v05-domain-existence.js +0 -23
- package/dist/core/catalog/checks/v05-domain-existence.js.map +0 -1
- package/dist/core/catalog/checks/v06-v07-paths.d.ts +0 -29
- package/dist/core/catalog/checks/v06-v07-paths.d.ts.map +0 -1
- package/dist/core/catalog/checks/v06-v07-paths.js +0 -107
- package/dist/core/catalog/checks/v06-v07-paths.js.map +0 -1
- package/dist/core/catalog/checks/v08-v10-contracts.d.ts +0 -13
- package/dist/core/catalog/checks/v08-v10-contracts.d.ts.map +0 -1
- package/dist/core/catalog/checks/v08-v10-contracts.js +0 -70
- package/dist/core/catalog/checks/v08-v10-contracts.js.map +0 -1
- package/dist/core/catalog/checks/v11-manual-fields.d.ts +0 -16
- package/dist/core/catalog/checks/v11-manual-fields.d.ts.map +0 -1
- package/dist/core/catalog/checks/v11-manual-fields.js +0 -60
- package/dist/core/catalog/checks/v11-manual-fields.js.map +0 -1
- package/dist/core/catalog/checks/v12-cycles.d.ts +0 -8
- package/dist/core/catalog/checks/v12-cycles.d.ts.map +0 -1
- package/dist/core/catalog/checks/v12-cycles.js +0 -28
- package/dist/core/catalog/checks/v12-cycles.js.map +0 -1
- package/dist/core/catalog/checks/v13-orphan-contracts.d.ts +0 -7
- package/dist/core/catalog/checks/v13-orphan-contracts.d.ts.map +0 -1
- package/dist/core/catalog/checks/v13-orphan-contracts.js +0 -33
- package/dist/core/catalog/checks/v13-orphan-contracts.js.map +0 -1
- package/dist/core/catalog/checks/v14-v15-lifecycle.d.ts +0 -8
- package/dist/core/catalog/checks/v14-v15-lifecycle.d.ts.map +0 -1
- package/dist/core/catalog/checks/v14-v15-lifecycle.js +0 -42
- package/dist/core/catalog/checks/v14-v15-lifecycle.js.map +0 -1
- package/dist/core/catalog/checks/v16-deprecated-consumers.d.ts +0 -7
- package/dist/core/catalog/checks/v16-deprecated-consumers.d.ts.map +0 -1
- package/dist/core/catalog/checks/v16-deprecated-consumers.js +0 -47
- package/dist/core/catalog/checks/v16-deprecated-consumers.js.map +0 -1
- package/dist/core/catalog/checks/v17-low-confidence.d.ts +0 -7
- package/dist/core/catalog/checks/v17-low-confidence.d.ts.map +0 -1
- package/dist/core/catalog/checks/v17-low-confidence.js +0 -32
- package/dist/core/catalog/checks/v17-low-confidence.js.map +0 -1
- package/dist/core/catalog/checks/v18-low-payload.d.ts +0 -7
- package/dist/core/catalog/checks/v18-low-payload.d.ts.map +0 -1
- package/dist/core/catalog/checks/v18-low-payload.js +0 -33
- package/dist/core/catalog/checks/v18-low-payload.js.map +0 -1
- package/dist/core/catalog/checks/v19-domain-membership.d.ts +0 -8
- package/dist/core/catalog/checks/v19-domain-membership.d.ts.map +0 -1
- package/dist/core/catalog/checks/v19-domain-membership.js +0 -55
- package/dist/core/catalog/checks/v19-domain-membership.js.map +0 -1
- package/dist/core/catalog/coverage.d.ts +0 -39
- package/dist/core/catalog/coverage.d.ts.map +0 -1
- package/dist/core/catalog/coverage.js +0 -62
- package/dist/core/catalog/coverage.js.map +0 -1
- package/dist/core/catalog/graph.d.ts +0 -49
- package/dist/core/catalog/graph.d.ts.map +0 -1
- package/dist/core/catalog/graph.js +0 -114
- package/dist/core/catalog/graph.js.map +0 -1
- package/dist/core/catalog/index-model.d.ts +0 -96
- package/dist/core/catalog/index-model.d.ts.map +0 -1
- package/dist/core/catalog/index-model.js +0 -8
- package/dist/core/catalog/index-model.js.map +0 -1
- package/dist/core/catalog/index.d.ts +0 -5
- package/dist/core/catalog/index.d.ts.map +0 -1
- package/dist/core/catalog/index.js +0 -2
- package/dist/core/catalog/index.js.map +0 -1
- package/dist/core/catalog/queries.d.ts +0 -69
- package/dist/core/catalog/queries.d.ts.map +0 -1
- package/dist/core/catalog/queries.js +0 -165
- package/dist/core/catalog/queries.js.map +0 -1
- package/dist/core/catalog/resolve.d.ts +0 -47
- package/dist/core/catalog/resolve.d.ts.map +0 -1
- package/dist/core/catalog/resolve.js +0 -318
- package/dist/core/catalog/resolve.js.map +0 -1
- package/dist/core/catalog/scaffold.d.ts +0 -31
- package/dist/core/catalog/scaffold.d.ts.map +0 -1
- package/dist/core/catalog/scaffold.js +0 -141
- package/dist/core/catalog/scaffold.js.map +0 -1
- package/dist/core/catalog/validate-component.d.ts +0 -50
- package/dist/core/catalog/validate-component.d.ts.map +0 -1
- package/dist/core/catalog/validate-component.js +0 -105
- package/dist/core/catalog/validate-component.js.map +0 -1
- package/dist/core/catalog/validate.d.ts +0 -71
- package/dist/core/catalog/validate.d.ts.map +0 -1
- package/dist/core/catalog/validate.js +0 -103
- package/dist/core/catalog/validate.js.map +0 -1
- package/dist/core/context/assemble.d.ts +0 -126
- package/dist/core/context/assemble.d.ts.map +0 -1
- package/dist/core/context/assemble.js +0 -197
- package/dist/core/context/assemble.js.map +0 -1
- package/dist/core/context/cache.d.ts +0 -60
- package/dist/core/context/cache.d.ts.map +0 -1
- package/dist/core/context/cache.js +0 -236
- package/dist/core/context/cache.js.map +0 -1
- package/dist/core/context/exit-codes.d.ts +0 -28
- package/dist/core/context/exit-codes.d.ts.map +0 -1
- package/dist/core/context/exit-codes.js +0 -28
- package/dist/core/context/exit-codes.js.map +0 -1
- package/dist/core/context/fetch.d.ts +0 -55
- package/dist/core/context/fetch.d.ts.map +0 -1
- package/dist/core/context/fetch.js +0 -112
- package/dist/core/context/fetch.js.map +0 -1
- package/dist/core/context/index.d.ts +0 -11
- package/dist/core/context/index.d.ts.map +0 -1
- package/dist/core/context/index.js +0 -8
- package/dist/core/context/index.js.map +0 -1
- package/dist/core/context/init.d.ts +0 -179
- package/dist/core/context/init.d.ts.map +0 -1
- package/dist/core/context/init.js +0 -532
- package/dist/core/context/init.js.map +0 -1
- package/dist/core/context/layers/architecture-layer.d.ts +0 -13
- package/dist/core/context/layers/architecture-layer.d.ts.map +0 -1
- package/dist/core/context/layers/architecture-layer.js +0 -24
- package/dist/core/context/layers/architecture-layer.js.map +0 -1
- package/dist/core/context/layers/contracts-layer.d.ts +0 -13
- package/dist/core/context/layers/contracts-layer.d.ts.map +0 -1
- package/dist/core/context/layers/contracts-layer.js +0 -83
- package/dist/core/context/layers/contracts-layer.js.map +0 -1
- package/dist/core/context/layers/conventions-delta-layer.d.ts +0 -13
- package/dist/core/context/layers/conventions-delta-layer.d.ts.map +0 -1
- package/dist/core/context/layers/conventions-delta-layer.js +0 -37
- package/dist/core/context/layers/conventions-delta-layer.js.map +0 -1
- package/dist/core/context/layers/flow-layer.d.ts +0 -14
- package/dist/core/context/layers/flow-layer.d.ts.map +0 -1
- package/dist/core/context/layers/flow-layer.js +0 -61
- package/dist/core/context/layers/flow-layer.js.map +0 -1
- package/dist/core/context/layers/index-layer.d.ts +0 -13
- package/dist/core/context/layers/index-layer.d.ts.map +0 -1
- package/dist/core/context/layers/index-layer.js +0 -77
- package/dist/core/context/layers/index-layer.js.map +0 -1
- package/dist/core/context/layers/primary-layer.d.ts +0 -16
- package/dist/core/context/layers/primary-layer.d.ts.map +0 -1
- package/dist/core/context/layers/primary-layer.js +0 -61
- package/dist/core/context/layers/primary-layer.js.map +0 -1
- package/dist/core/context/layers/secondary-layer.d.ts +0 -19
- package/dist/core/context/layers/secondary-layer.d.ts.map +0 -1
- package/dist/core/context/layers/secondary-layer.js +0 -52
- package/dist/core/context/layers/secondary-layer.js.map +0 -1
- package/dist/core/context/session-lock.d.ts +0 -114
- package/dist/core/context/session-lock.d.ts.map +0 -1
- package/dist/core/context/session-lock.js +0 -90
- package/dist/core/context/session-lock.js.map +0 -1
- package/dist/core/context/tokens.d.ts +0 -35
- package/dist/core/context/tokens.d.ts.map +0 -1
- package/dist/core/context/tokens.js +0 -88
- package/dist/core/context/tokens.js.map +0 -1
- package/dist/core/extract/asyncapi/declared.d.ts +0 -19
- package/dist/core/extract/asyncapi/declared.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/declared.js +0 -168
- package/dist/core/extract/asyncapi/declared.js.map +0 -1
- package/dist/core/extract/asyncapi/index.d.ts +0 -12
- package/dist/core/extract/asyncapi/index.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/index.js +0 -8
- package/dist/core/extract/asyncapi/index.js.map +0 -1
- package/dist/core/extract/asyncapi/payloads.d.ts +0 -20
- package/dist/core/extract/asyncapi/payloads.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/payloads.js +0 -421
- package/dist/core/extract/asyncapi/payloads.js.map +0 -1
- package/dist/core/extract/asyncapi/topics.d.ts +0 -27
- package/dist/core/extract/asyncapi/topics.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/topics.js +0 -368
- package/dist/core/extract/asyncapi/topics.js.map +0 -1
- package/dist/core/extract/asyncapi/types.d.ts +0 -129
- package/dist/core/extract/asyncapi/types.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/types.js +0 -5
- package/dist/core/extract/asyncapi/types.js.map +0 -1
- package/dist/core/extract/asyncapi/validate.d.ts +0 -29
- package/dist/core/extract/asyncapi/validate.d.ts.map +0 -1
- package/dist/core/extract/asyncapi/validate.js +0 -156
- package/dist/core/extract/asyncapi/validate.js.map +0 -1
- package/dist/core/extract/component.d.ts +0 -204
- package/dist/core/extract/component.d.ts.map +0 -1
- package/dist/core/extract/component.js +0 -258
- package/dist/core/extract/component.js.map +0 -1
- package/dist/core/extract/detect.d.ts +0 -35
- package/dist/core/extract/detect.d.ts.map +0 -1
- package/dist/core/extract/detect.js +0 -89
- package/dist/core/extract/detect.js.map +0 -1
- package/dist/core/extract/index.d.ts +0 -12
- package/dist/core/extract/index.d.ts.map +0 -1
- package/dist/core/extract/index.js +0 -6
- package/dist/core/extract/index.js.map +0 -1
- package/dist/core/extract/ladder.d.ts +0 -79
- package/dist/core/extract/ladder.d.ts.map +0 -1
- package/dist/core/extract/ladder.js +0 -70
- package/dist/core/extract/ladder.js.map +0 -1
- package/dist/core/extract/openapi/index.d.ts +0 -43
- package/dist/core/extract/openapi/index.d.ts.map +0 -1
- package/dist/core/extract/openapi/index.js +0 -142
- package/dist/core/extract/openapi/index.js.map +0 -1
- package/dist/core/extract/openapi/route1.d.ts +0 -36
- package/dist/core/extract/openapi/route1.d.ts.map +0 -1
- package/dist/core/extract/openapi/route1.js +0 -333
- package/dist/core/extract/openapi/route1.js.map +0 -1
- package/dist/core/extract/openapi/route2-introspect.d.ts +0 -18
- package/dist/core/extract/openapi/route2-introspect.d.ts.map +0 -1
- package/dist/core/extract/openapi/route2-introspect.js +0 -249
- package/dist/core/extract/openapi/route2-introspect.js.map +0 -1
- package/dist/core/extract/openapi/route2.d.ts +0 -69
- package/dist/core/extract/openapi/route2.d.ts.map +0 -1
- package/dist/core/extract/openapi/route2.js +0 -211
- package/dist/core/extract/openapi/route2.js.map +0 -1
- package/dist/core/extract/openapi/route3.d.ts +0 -26
- package/dist/core/extract/openapi/route3.d.ts.map +0 -1
- package/dist/core/extract/openapi/route3.js +0 -737
- package/dist/core/extract/openapi/route3.js.map +0 -1
- package/dist/core/extract/openapi/types.d.ts +0 -125
- package/dist/core/extract/openapi/types.d.ts.map +0 -1
- package/dist/core/extract/openapi/types.js +0 -5
- package/dist/core/extract/openapi/types.js.map +0 -1
- package/dist/core/extract/openapi/validate.d.ts +0 -29
- package/dist/core/extract/openapi/validate.d.ts.map +0 -1
- package/dist/core/extract/openapi/validate.js +0 -200
- package/dist/core/extract/openapi/validate.js.map +0 -1
- package/dist/core/extract/orm/drizzle.d.ts +0 -20
- package/dist/core/extract/orm/drizzle.d.ts.map +0 -1
- package/dist/core/extract/orm/drizzle.js +0 -283
- package/dist/core/extract/orm/drizzle.js.map +0 -1
- package/dist/core/extract/orm/information-schema.d.ts +0 -26
- package/dist/core/extract/orm/information-schema.d.ts.map +0 -1
- package/dist/core/extract/orm/information-schema.js +0 -142
- package/dist/core/extract/orm/information-schema.js.map +0 -1
- package/dist/core/extract/orm/prisma.d.ts +0 -23
- package/dist/core/extract/orm/prisma.d.ts.map +0 -1
- package/dist/core/extract/orm/prisma.js +0 -234
- package/dist/core/extract/orm/prisma.js.map +0 -1
- package/dist/core/extract/orm/typeorm.d.ts +0 -22
- package/dist/core/extract/orm/typeorm.d.ts.map +0 -1
- package/dist/core/extract/orm/typeorm.js +0 -269
- package/dist/core/extract/orm/typeorm.js.map +0 -1
- package/dist/core/extract/orm/types.d.ts +0 -97
- package/dist/core/extract/orm/types.d.ts.map +0 -1
- package/dist/core/extract/orm/types.js +0 -6
- package/dist/core/extract/orm/types.js.map +0 -1
- package/dist/core/extract/prompt.d.ts +0 -21
- package/dist/core/extract/prompt.d.ts.map +0 -1
- package/dist/core/extract/prompt.js +0 -79
- package/dist/core/extract/prompt.js.map +0 -1
- package/dist/core/extract/provider.d.ts +0 -121
- package/dist/core/extract/provider.d.ts.map +0 -1
- package/dist/core/extract/provider.js +0 -6
- package/dist/core/extract/provider.js.map +0 -1
- package/dist/core/extract/providers/node-ts.d.ts +0 -69
- package/dist/core/extract/providers/node-ts.d.ts.map +0 -1
- package/dist/core/extract/providers/node-ts.js +0 -320
- package/dist/core/extract/providers/node-ts.js.map +0 -1
- package/dist/core/extract/render/schema-md.d.ts +0 -16
- package/dist/core/extract/render/schema-md.d.ts.map +0 -1
- package/dist/core/extract/render/schema-md.js +0 -140
- package/dist/core/extract/render/schema-md.js.map +0 -1
- package/dist/core/extract/report.d.ts +0 -125
- package/dist/core/extract/report.d.ts.map +0 -1
- package/dist/core/extract/report.js +0 -52
- package/dist/core/extract/report.js.map +0 -1
- package/dist/core/extract/schema.d.ts +0 -34
- package/dist/core/extract/schema.d.ts.map +0 -1
- package/dist/core/extract/schema.js +0 -146
- package/dist/core/extract/schema.js.map +0 -1
- package/dist/core/extract/workspaces.d.ts +0 -33
- package/dist/core/extract/workspaces.d.ts.map +0 -1
- package/dist/core/extract/workspaces.js +0 -193
- package/dist/core/extract/workspaces.js.map +0 -1
- package/dist/core/providers/index.d.ts +0 -6
- package/dist/core/providers/index.d.ts.map +0 -1
- package/dist/core/providers/index.js +0 -2
- package/dist/core/providers/index.js.map +0 -1
- package/dist/core/providers/tracker.d.ts +0 -74
- package/dist/core/providers/tracker.d.ts.map +0 -1
- package/dist/core/providers/tracker.js +0 -38
- package/dist/core/providers/tracker.js.map +0 -1
- package/dist/core/scope/calibration.d.ts +0 -25
- package/dist/core/scope/calibration.d.ts.map +0 -1
- package/dist/core/scope/calibration.js +0 -52
- package/dist/core/scope/calibration.js.map +0 -1
- package/dist/core/scope/closure.d.ts +0 -31
- package/dist/core/scope/closure.d.ts.map +0 -1
- package/dist/core/scope/closure.js +0 -68
- package/dist/core/scope/closure.js.map +0 -1
- package/dist/core/scope/gate.d.ts +0 -41
- package/dist/core/scope/gate.d.ts.map +0 -1
- package/dist/core/scope/gate.js +0 -165
- package/dist/core/scope/gate.js.map +0 -1
- package/dist/core/scope/index.d.ts +0 -18
- package/dist/core/scope/index.d.ts.map +0 -1
- package/dist/core/scope/index.js +0 -12
- package/dist/core/scope/index.js.map +0 -1
- package/dist/core/scope/partition.d.ts +0 -36
- package/dist/core/scope/partition.d.ts.map +0 -1
- package/dist/core/scope/partition.js +0 -78
- package/dist/core/scope/partition.js.map +0 -1
- package/dist/core/scope/prompt.d.ts +0 -39
- package/dist/core/scope/prompt.d.ts.map +0 -1
- package/dist/core/scope/prompt.js +0 -123
- package/dist/core/scope/prompt.js.map +0 -1
- package/dist/core/scope/scoping.d.ts +0 -52
- package/dist/core/scope/scoping.d.ts.map +0 -1
- package/dist/core/scope/scoping.js +0 -99
- package/dist/core/scope/scoping.js.map +0 -1
- package/dist/core/scope/types.d.ts +0 -77
- package/dist/core/scope/types.d.ts.map +0 -1
- package/dist/core/scope/types.js +0 -5
- package/dist/core/scope/types.js.map +0 -1
- package/dist/core/scope/validate.d.ts +0 -47
- package/dist/core/scope/validate.d.ts.map +0 -1
- package/dist/core/scope/validate.js +0 -90
- package/dist/core/scope/validate.js.map +0 -1
- package/dist/core/verify/asyncapi-diff.d.ts +0 -34
- package/dist/core/verify/asyncapi-diff.d.ts.map +0 -1
- package/dist/core/verify/asyncapi-diff.js +0 -209
- package/dist/core/verify/asyncapi-diff.js.map +0 -1
- package/dist/core/verify/contract-diff.d.ts +0 -39
- package/dist/core/verify/contract-diff.d.ts.map +0 -1
- package/dist/core/verify/contract-diff.js +0 -63
- package/dist/core/verify/contract-diff.js.map +0 -1
- package/dist/core/verify/drift.d.ts +0 -47
- package/dist/core/verify/drift.d.ts.map +0 -1
- package/dist/core/verify/drift.js +0 -122
- package/dist/core/verify/drift.js.map +0 -1
- package/dist/core/verify/impact.d.ts +0 -22
- package/dist/core/verify/impact.d.ts.map +0 -1
- package/dist/core/verify/impact.js +0 -93
- package/dist/core/verify/impact.js.map +0 -1
- package/dist/core/verify/index.d.ts +0 -10
- package/dist/core/verify/index.d.ts.map +0 -1
- package/dist/core/verify/index.js +0 -9
- package/dist/core/verify/index.js.map +0 -1
- package/dist/core/verify/openapi-diff.d.ts +0 -29
- package/dist/core/verify/openapi-diff.d.ts.map +0 -1
- package/dist/core/verify/openapi-diff.js +0 -291
- package/dist/core/verify/openapi-diff.js.map +0 -1
- package/dist/core/verify/types.d.ts +0 -138
- package/dist/core/verify/types.d.ts.map +0 -1
- package/dist/core/verify/types.js +0 -5
- package/dist/core/verify/types.js.map +0 -1
- package/schemas/component.schema.json +0 -203
- package/schemas/flow.schema.json +0 -75
- package/schemas/scope-output.schema.json +0 -62
|
@@ -7,6 +7,8 @@ description: "Transform an approved PRD into a technical specification. Use in p
|
|
|
7
7
|
|
|
8
8
|
Transform refined requirements (PRD) into an actionable technical design by synthesizing them with the project's Technical Guidelines. Use this skill when a PRD is approved and ready for technical breakdown. Invoked by the `product-engineer` agent in Feature Mode.
|
|
9
9
|
|
|
10
|
+
Before asking any technical design question, this activity invokes the `activity-grill` sub-skill (HOW phase) to walk the design tree to shared understanding, and writes every resolved question to `workstream/decisions-<feature>.md` — see Process below. `product-engineer`'s own conditional pre-step `researcher` call (ADR-004) runs before this activity starts, not after; when its `/workstream/research-*.md` artifact exists, `activity-grill`'s resolve-before-ask step consults it before making its own bounded call (D-56).
|
|
11
|
+
|
|
10
12
|
---
|
|
11
13
|
|
|
12
14
|
> **RFC 2119 Notice:** The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119).
|
|
@@ -19,8 +21,8 @@ Transform refined requirements (PRD) into an actionable technical design by synt
|
|
|
19
21
|
|
|
20
22
|
This activity assumes the following documents already exist:
|
|
21
23
|
|
|
22
|
-
- `product
|
|
23
|
-
- `
|
|
24
|
+
- `product.md` — Product understanding
|
|
25
|
+
- `tech.md` — Technical standards and patterns
|
|
24
26
|
- `prd-[feature-name].md` — Feature requirements (produced by the **refine** activity)
|
|
25
27
|
|
|
26
28
|
## Document Changelog Convention
|
|
@@ -42,13 +44,13 @@ Every specification produced by this activity **MUST** include a **Changelog** t
|
|
|
42
44
|
|
|
43
45
|
## Process
|
|
44
46
|
|
|
45
|
-
1. **Receive References:** User points to the existing PRD and confirms Technical Guidelines are available.
|
|
47
|
+
1. **Receive References:** User points to the existing PRD and confirms Technical Guidelines are available. If a pre-step `researcher` artifact (`/workstream/research-*.md`) exists from `product-engineer`'s conditional pre-step call (ADR-004), treat it as already available evidence.
|
|
46
48
|
2. **Analyze Documents:** You **MUST** read and analyze both the PRD and Technical Guidelines to identify integration points.
|
|
47
|
-
3. **
|
|
48
|
-
4. **Generate Specification:** You **MUST** create a comprehensive technical specification using the structure below.
|
|
49
|
+
3. **Invoke `activity-grill`:** Before asking any technical design question, invoke `activity-grill(phase="HOW", cap=cap.how)` (`cap.how` defaults to 25; read from `docs/tech.md` § Grilling if that subsection exists, else the hardcoded default) (FR-13, AC-02). The candidate questions below seed the interview's question pool — `activity-grill` owns the one-question-at-a-time, resolve-before-ask mechanics, including reuse of any pre-step `researcher` artifact and, only when that artifact does not cover a question, its own bounded `researcher` call sharing the phase's budget (D-56). You **MUST NOT** produce any specification section, draft, or outline until `activity-grill` returns the exit gate satisfied.
|
|
50
|
+
4. **Generate Specification:** You **MUST** create a comprehensive technical specification using the structure below, citing inline (`… (D-NN)`) every technical decision a `D-NN` shaped.
|
|
49
51
|
5. **Save Output.**
|
|
50
52
|
|
|
51
|
-
##
|
|
53
|
+
## Candidate Specification Questions (seed the `activity-grill` interview)
|
|
52
54
|
|
|
53
55
|
Focus on technical decisions and implementation approach:
|
|
54
56
|
|
|
@@ -87,6 +89,26 @@ The generated Specification document **MUST** include:
|
|
|
87
89
|
15. **Deployment & Rollout** — Feature flags, migration steps, backward compatibility, rollback plan
|
|
88
90
|
16. **Dependencies & Risks** — Technology dependencies, known risks, mitigation strategies
|
|
89
91
|
17. **Open Questions** — Remaining technical decisions
|
|
92
|
+
18. **Decisions (HOW phase)** — Table (`ID | Decision (short form)`) listing every `activity-grill` decision ID consumed by this specification (FR-14, S-003-AC-3), in qualified `<feature>#D-NN` form when reusing a decision from another feature's log; may legitimately be empty for a trivial specification that needed no decisions, but the `activity-grill` interview and exit-gate confirmation still ran
|
|
93
|
+
19. **Vocabulary** — `## Vocabulary` table listing every domain term the specification uses and where each one stands against the glossary: `existing`, `proposed`, or settled by a decision (FR-20, D-61). See "Vocabulary Section" below
|
|
94
|
+
|
|
95
|
+
## Vocabulary Section (FR-20, D-61, D-75)
|
|
96
|
+
|
|
97
|
+
The specification carries a `## Vocabulary` section immediately after `## Decisions (HOW phase)`, in the same shape `activity-refine` uses for PRDs:
|
|
98
|
+
|
|
99
|
+
```markdown
|
|
100
|
+
## Vocabulary
|
|
101
|
+
|
|
102
|
+
| Term | Status in glossary | Bounded context | Definition (proposals only) | Forbidden synonyms (proposals only) |
|
|
103
|
+
| ---- | --------------------------------------- | --------------- | --------------------------- | ----------------------------------- |
|
|
104
|
+
| … | existing \| proposed \| conflict → D-NN | … | … | … |
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
A row is complete when `existing` names a term `docs/domain/ubiquitous-language.md` already defines (case-insensitively), when `proposed` carries a bounded context, a definition, and forbidden synonyms (`none` is an answer), or when `conflict → D-NN` cites the decision that settled a clash — `->` and `→` are both accepted. A specification that introduces no domain concept of its own carries the section with exactly one line, and that line **MUST** be the section's only content — the sentinel is accepted only when nothing else stands beside it (a `None — …` sentence above a table does not make the table complete): `None — this specification introduces no domain concepts.`
|
|
108
|
+
|
|
109
|
+
A specification introduces implementation vocabulary as readily as a PRD introduces product vocabulary, and the term that enters the codebase through a module name is the one nobody ever agreed on. Terms are identified during HOW-phase grilling, never by scanning the drafted prose (D-65).
|
|
110
|
+
|
|
111
|
+
The glossary append itself is `activity-refine`'s write at PRD approval, not this skill's (D-61). A term a specification proposes is carried back to the PRD's `## Vocabulary` section for approval.
|
|
90
112
|
|
|
91
113
|
## Diagram Guidelines
|
|
92
114
|
|
|
@@ -130,8 +152,10 @@ The specification **MUST** clearly show how:
|
|
|
130
152
|
|
|
131
153
|
1. You **MUST NOT** start implementing.
|
|
132
154
|
2. You **MUST** read the referenced PRD and Technical Guidelines documents.
|
|
133
|
-
3. You **
|
|
155
|
+
3. You **MUST** ask clarifying questions about the technical implementation approach, conducted through `activity-grill(phase="HOW")` — you **MUST NOT** draft any part of the specification until `activity-grill`'s exit gate returns satisfied (FR-13).
|
|
134
156
|
4. You **MUST** ensure the specification clearly maps PRD requirements to technical solutions.
|
|
135
|
-
5.
|
|
136
|
-
6. You **MUST**
|
|
137
|
-
7.
|
|
157
|
+
5. Before presenting the specification for review, you **MUST** run `checkVocabularySection()` from `core/checks/glossary.ts` over the draft and the repository's glossary, and **MUST** report every finding by its rule name — `vocabulary-missing` or `vocabulary-incomplete` naming the row (D-75).
|
|
158
|
+
6. You **MUST** present the specification for user review.
|
|
159
|
+
7. You **MUST** save the finalized version.
|
|
160
|
+
8. When updating an existing specification, you **MUST** add a new row to the Changelog table with an incremented version, the current date, a summary of changes, and the responsible author/agent.
|
|
161
|
+
9. You **MUST** cite every decision that shaped a technical design choice inline (`… (D-NN)`), and **MUST** populate the document's `## Decisions (HOW phase)` section with every ID consumed from the `activity-grill` session, in qualified `<feature>#D-NN` form when reusing a decision from another feature's log (FR-14).
|
|
@@ -0,0 +1,150 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: activity-grill
|
|
3
|
+
description: "Interview the user one question at a time, depth-first, resolve-before-ask, until every open design question is resolved and the user explicitly confirms shared understanding. Invoked by activity-refine (WHAT phase, Issue Mode) and activity-generate-spec (HOW phase)."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Activity: Grill
|
|
7
|
+
|
|
8
|
+
Interview the user one question at a time — depth-first, resolve-before-ask, one recommendation per question — until every open design question is resolved and the user has explicitly confirmed shared understanding. `activity-grill` is a sub-skill invoked by `activity-refine` (WHAT phase, Issue Mode) and `activity-generate-spec` (HOW phase); it has no top-level entry point of its own.
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
> **RFC 2119 Notice:** The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119).
|
|
13
|
+
|
|
14
|
+
## Goal
|
|
15
|
+
|
|
16
|
+
Walk the design tree for a feature or issue to a state of genuine shared understanding, recorded as an auditable decision log, before the invoking skill drafts anything. The engine never batches questions, never infers confirmation from tone, and never silently decides on the user's behalf.
|
|
17
|
+
|
|
18
|
+
## Invocation
|
|
19
|
+
|
|
20
|
+
The caller passes:
|
|
21
|
+
|
|
22
|
+
- `phase` — `"WHAT"` (invoked by `activity-refine` PRD Creation mode, before drafting) or `"HOW"` (invoked by `activity-generate-spec`, before drafting). Both phases share one continuing ID space in the decision log — there is no phase-local restart (FR-7).
|
|
23
|
+
- `cap` — the question cap for this phase (see Cap Configuration below).
|
|
24
|
+
- `mode` — `"feature"` (default) or `"issue"` (Issue Mode, invoked by `activity-refine` Issue Refinement mode). Issue Mode is invoked without a `phase` argument — `activity-refine` passes `mode` and `cap` only.
|
|
25
|
+
- `feature` — the slug used to name `workstream/decisions-<feature>.md`.
|
|
26
|
+
|
|
27
|
+
## Context
|
|
28
|
+
|
|
29
|
+
This skill has no caller-specific behavior of its own — `activity-refine` and `activity-generate-spec` decide when to invoke it and what to do with a satisfied exit gate. This skill owns only: the question loop, resolve-before-ask precedence, the append-per-resolution write, the cap/summary/exit-gate mechanics, and the Issue Mode variant.
|
|
30
|
+
|
|
31
|
+
## Write Authority
|
|
32
|
+
|
|
33
|
+
- `workstream/decisions-<feature>.md` — append one row per resolved question, immediately (FR-4). Never batch writes to the end of a session.
|
|
34
|
+
- Nothing else. No PRD, spec, task list, code, or `/DESIGN.md` file may be created or modified by this skill.
|
|
35
|
+
|
|
36
|
+
## Process
|
|
37
|
+
|
|
38
|
+
### 1. One question, one recommendation, per turn (FR-1)
|
|
39
|
+
|
|
40
|
+
The skill never batches questions in one turn. Each question the skill cannot resolve itself is presented alone, with exactly one recommended answer attached, so the user can accept the recommendation or state a different answer in a single reply.
|
|
41
|
+
|
|
42
|
+
### 2. Depth-first traversal (FR-2)
|
|
43
|
+
|
|
44
|
+
A branch (e.g., `grilling/placement`, `simplicity/content` — the existing `Branch` column in `decisions-<feature>.md` already models this) is fully resolved, including any decision it depends on, before a sibling branch opens. Do not open a new branch while the current one has unresolved dependents.
|
|
45
|
+
|
|
46
|
+
### 3. Resolve-before-ask (FR-3)
|
|
47
|
+
|
|
48
|
+
Before asking the user anything, check in this order:
|
|
49
|
+
|
|
50
|
+
1. **Codebase directly** — `Read`/`Grep`/`Glob` for single-file questions (e.g., "does this config already exist?").
|
|
51
|
+
2. **`docs/product.md` / `docs/tech.md` / the glossary** for standing decisions already recorded there. All three are read here and written by none of them — the glossary in particular is consulted, never edited, in every mode (D-61).
|
|
52
|
+
3. **Prior `decisions-*.md` files** for a matching answer — mandatory in Issue Mode (FR-10), optional-but-recommended in Feature Mode.
|
|
53
|
+
4. **A bounded `researcher` call** — only when the question needs multi-slice evidence a single file read cannot supply, AND only if a fresh, non-stale pre-step `/workstream/research-*.md` artifact (if any) does not already cover it (D-56). At most one `researcher` call total per phase, shared with the caller's own conditional pre-step budget (ADR-004) — `activity-grill` is a second possible caller of `researcher`, not a second guaranteed invocation.
|
|
54
|
+
|
|
55
|
+
Only if none of the four resolve the question does the skill ask the user. A question whose codebase answer is ambiguous (multiple conflicting sources) is still asked to the user — the skill never guesses.
|
|
56
|
+
|
|
57
|
+
### 3a. Vocabulary conflicts are questions, never resolutions (FR-21)
|
|
58
|
+
|
|
59
|
+
This rule belongs to the two invocations where the feature's domain language is still being settled: the WHAT phase (`phase="WHAT"`) and Issue Mode (`mode="issue"`, which `activity-refine` invokes without a `phase` argument — see step 10). It does not run in the HOW phase.
|
|
60
|
+
|
|
61
|
+
Once the open branch reaches what the feature _is_, ask the user plainly **which domain concepts this feature introduces or changes** — one question, with a recommendation, like every other. For each term the user names, consult the glossary (step 3's second source) and check two things:
|
|
62
|
+
|
|
63
|
+
1. **The same term with a different definition** — the glossary already defines the term, and the definition the user just gave is not the recorded one.
|
|
64
|
+
2. **The term appearing in another term's forbidden synonyms** — the term is not an entry of its own, but an existing entry names it as a synonym it forbids.
|
|
65
|
+
|
|
66
|
+
Either hit is **surfaced as a question** with exactly one recommendation, and the user's answer becomes a `D-NN` row like any other resolution (step 4). A conflict is **never resolved silently**: the skill does not adopt the glossary's definition, does not adopt the user's, and does not quietly rename or merge the term. The term's `Status in glossary` is then `conflict → D-NN` in the drafted PRD — written later, by the caller, not here.
|
|
67
|
+
|
|
68
|
+
Two cases resolve without a new question, or with one question rather than several:
|
|
69
|
+
|
|
70
|
+
- **Same term, same definition.** The glossary already says what the user just said; nothing is asked and the existing term is reused. That is resolve-before-ask working (step 3), not a conflict.
|
|
71
|
+
- **One term forbidden by two entries.** A term named as a forbidden synonym by two different glossary entries raises **one** question naming both owning terms — one conflict with two owners, not two conflicts. Batching remains forbidden (FR-1).
|
|
72
|
+
|
|
73
|
+
The skill reads the glossary and writes nothing to it, in every mode and every phase — see Write Authority.
|
|
74
|
+
|
|
75
|
+
### 4. Append-per-resolution (FR-4)
|
|
76
|
+
|
|
77
|
+
Every resolved question — whether asked to the user or self-resolved via step 3 — becomes one row in `workstream/decisions-<feature>.md`, written immediately, not batched at the end of the session. A self-resolved row still gets a unique, never-reused `D-NN` ID; its `Accepted rec.` column is `n/a` and its `Answer` column states what was found and where (file, section, or prior decision ID). Row columns: ID, Phase, Branch, Question, Recommended, Answer, Accepted rec., Supersedes, Author, Date — the existing `decisions-<feature>.md` schema, unchanged by this skill.
|
|
78
|
+
|
|
79
|
+
### 5. Qualified citation form (FR-5)
|
|
80
|
+
|
|
81
|
+
Cite a decision as `<feature>#D-NN` everywhere outside that decision's own log file, and as the unqualified `D-NN` inside it — the convention `decisions-shared-understanding.md` already uses. A corrected decision never overwrites or renumbers its original row; it gets a new row whose `Supersedes` column names the superseded ID.
|
|
82
|
+
|
|
83
|
+
### 6. Decision-tree summary cadence (FR-6)
|
|
84
|
+
|
|
85
|
+
Every 10th resolved question, at the cap, and at the exit-gate attempt, the skill prints a decision-tree summary: resolved branches (each with its `D-NN`), the current branch, and the remaining open list. This is the only place the skill surfaces multiple prior questions at once — it is a summary of what already happened, not a new batch of questions.
|
|
86
|
+
|
|
87
|
+
### 7. Two-phase mode (FR-7)
|
|
88
|
+
|
|
89
|
+
`activity-grill(phase="WHAT")` runs before `activity-refine` drafts a PRD; `activity-grill(phase="HOW")` runs before `activity-generate-spec` drafts a specification. Each phase's questions continue the single ID space already present in the feature's decision log (e.g., D-01…D-27 WHAT, D-28… HOW) — never a phase-local restart.
|
|
90
|
+
|
|
91
|
+
### 8. Hard exit gate (FR-8)
|
|
92
|
+
|
|
93
|
+
The exit gate is satisfied only when **both** hold:
|
|
94
|
+
|
|
95
|
+
- The open-questions list is empty, **and**
|
|
96
|
+
- The user has made an explicit statement of shared understanding (e.g., "I understand, proceed" / "I confirm").
|
|
97
|
+
|
|
98
|
+
A "sounds good," an emoji, or silence after a decision-tree summary does **not** satisfy the gate. When the open list is empty, the skill asks directly: _"The open list is empty. Do you confirm shared understanding so I can draft?"_ If the user's reply is not an explicit confirmation, the skill re-asks the same direct question rather than treating the reply as consent — the gate is never inferred from tone or silence.
|
|
99
|
+
|
|
100
|
+
An empty open-questions list at invocation (nothing to grill) does not silently skip this gate — the direct confirmation question is still asked and must still be explicitly answered.
|
|
101
|
+
|
|
102
|
+
### 9. Configurable, enforced cap (FR-9)
|
|
103
|
+
|
|
104
|
+
Default cap: **25/25/8** — 25 questions per phase in Feature Mode (WHAT, HOW), 8 in Issue Mode. Read the configured cap from `docs/tech.md` § Grilling if that subsection exists; otherwise use the hardcoded default. If the configured value is 0 or non-positive, treat it as misconfiguration: fall back to the hardcoded default and note the fallback in the next decision-tree summary.
|
|
105
|
+
|
|
106
|
+
On reaching the cap, the skill presents the open list and asks the user to **continue (raise the cap) or stop (draft with what's settled, leaving the rest as recorded Open Questions)**. It never auto-continues and never auto-stops — the choice belongs to the user every time the cap is reached.
|
|
107
|
+
|
|
108
|
+
### 10. Issue Mode constraints (FR-10)
|
|
109
|
+
|
|
110
|
+
When `mode="issue"`:
|
|
111
|
+
|
|
112
|
+
- **Glossary is read-only.** No new term proposals. The glossary is consulted for resolve-before-ask and for the conflict checks in step 3a; a term the issue needs and the glossary lacks is a question for the user, never an edit made here.
|
|
113
|
+
- **Scope is limited** to what the issue changes relative to current behavior — do not open branches outside that delta.
|
|
114
|
+
- **Prior-decision reuse is mandatory, not optional.** Before asking, search prior decisions from _any_ feature's `decisions-*.md` for a reusable answer. The scan is keyword-gated: only logs whose `Branch` or `Question` text shares a term with the issue description are read, keeping the lookup bounded as the number of logs grows. A reused answer is cited in qualified form (`<other-feature>#D-NN`) and is not re-asked.
|
|
115
|
+
- The cap is 8, per the default above (or the configured `docs/tech.md` § Grilling issue-mode value).
|
|
116
|
+
|
|
117
|
+
### 11. Assumption-testing reminder (FR-11, SHOULD)
|
|
118
|
+
|
|
119
|
+
Once per phase, the skill states plainly that accepting every recommendation reproduces its own assumptions rather than testing them — a reminder, not a gate, and not repeated more than once per phase.
|
|
120
|
+
|
|
121
|
+
## Cap Configuration
|
|
122
|
+
|
|
123
|
+
| Mode | Default cap | Configured source |
|
|
124
|
+
| ------------------ | ----------- | ------------------------------------- |
|
|
125
|
+
| Feature Mode, WHAT | 25 | `docs/tech.md` § Grilling, if present |
|
|
126
|
+
| Feature Mode, HOW | 25 | `docs/tech.md` § Grilling, if present |
|
|
127
|
+
| Issue Mode | 8 | `docs/tech.md` § Grilling, if present |
|
|
128
|
+
|
|
129
|
+
The 25/25/8 defaults apply whenever `docs/tech.md` has no § Grilling subsection, or the subsection's value for this mode is missing, zero, or negative (misconfiguration fallback, noted in the next decision-tree summary).
|
|
130
|
+
|
|
131
|
+
## Session State (D-54)
|
|
132
|
+
|
|
133
|
+
The open-questions list and the current depth-first tree position live only in the invoking conversation's turn-by-turn context. `workstream/decisions-<feature>.md` is the only persistent artifact this skill writes, appended to immediately per resolved question (FR-4). **Do not** create a separate `grill-state-<feature>.md` or any other working file to track session progress. If a session is interrupted and resumed, re-derive the open list by diffing what the PRD/spec still needs settled against what the decision log already has — the log is the source of truth for what is already resolved.
|
|
134
|
+
|
|
135
|
+
## Attribution (D-53)
|
|
136
|
+
|
|
137
|
+
No attribution is added anywhere in this skill for the `grill-me` interview pattern. This implementation is written independently from the PRD's own description of the desired behavior, not derived from any one repository's source; there is no single canonical `grill-me` project to credit, and several independent, differently-licensed reimplementations exist. Do not add a header credit line, footer note, or inline reference naming grill-me or any of its forks.
|
|
138
|
+
|
|
139
|
+
## Output
|
|
140
|
+
|
|
141
|
+
- Zero or more new rows appended to `workstream/decisions-<feature>.md`, one per resolved question, written as each question resolves.
|
|
142
|
+
- A returned exit-gate status to the caller: satisfied (open list empty and explicit confirmation received) or not yet satisfied.
|
|
143
|
+
- Zero or more decision-tree summaries printed to the conversation at the required cadence (every 10th resolution, cap, exit attempt).
|
|
144
|
+
|
|
145
|
+
## Non-Goals
|
|
146
|
+
|
|
147
|
+
- Not a drafting skill — produces no PRD, spec, or task-list content itself.
|
|
148
|
+
- Not a top-level entry point — only `activity-refine` and `activity-generate-spec` invoke it.
|
|
149
|
+
- Not a glossary editor — the glossary is read in every mode and written in none. Proposing a term into it is `activity-refine`'s write, made on the user's approval of a PRD, never mid-interview (D-61).
|
|
150
|
+
- Not a second, independent `researcher` budget — shares the phase's existing conditional pre-step budget (D-56, ADR-004).
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: activity-init
|
|
3
|
-
description: "Establish product
|
|
3
|
+
description: "Establish product.md and tech.md foundation docs. Use in product-engineer Init Mode."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Activity: Initialize Project Foundation
|
|
@@ -17,6 +17,27 @@ Guide an AI assistant in establishing the foundational documents for a project:
|
|
|
17
17
|
|
|
18
18
|
Run this activity **once per project** (or when a major strategic or technical pivot occurs).
|
|
19
19
|
|
|
20
|
+
## Foundation Document Names
|
|
21
|
+
|
|
22
|
+
The canonical names are **`docs/product.md`** and **`docs/tech.md`**. Create and reference those names only.
|
|
23
|
+
|
|
24
|
+
**Fallback, one release cycle (FR-45, `shared-understanding#D-42`).** These documents were renamed from `docs/product-context.md` and `docs/technical-guidelines.md`. A consumer repository installed before the rename still carries the old names, and `dev-tasks update` never renames a consumer-owned file on its own. So when reading a foundation document: resolve `docs/product.md` first and fall back to `docs/product-context.md` only if the new name is absent; likewise `docs/tech.md`, then `docs/technical-guidelines.md`. When writing, always write the new name.
|
|
25
|
+
|
|
26
|
+
On encountering the old names, propose `dev-tasks migrate docs`, which performs the rename with content unchanged. Do not rename a consumer's files without being asked. The fallback is removed one release cycle after the rename ships (tracked in issue #201); after that the proposal is the only path.
|
|
27
|
+
|
|
28
|
+
## Repository Setup — Branch Protection (Required)
|
|
29
|
+
|
|
30
|
+
Before or alongside establishing the foundation documents, verify the repository's default branch has GitHub branch protection configured. This is not optional hardening — it is the actual gate for "no agent merges into the default branch." Every hook shipped with dev-tasks (`git-guard.sh`, `branch-guard.sh`, and their Kiro equivalents) is a best-effort, advisory, local check that can be evaded by a sufficiently creative command or tool-input shape, and Copilot has no hook system at all; only a server-side branch protection rule is unbypassable by any tool surface.
|
|
31
|
+
|
|
32
|
+
Check with `gh api repos/<owner>/<repo>/branches/<default-branch>/protection` (a 404 means it is not configured). If missing, tell the user and offer to configure it:
|
|
33
|
+
|
|
34
|
+
- Require a pull request before merging
|
|
35
|
+
- Require at least 1 approving review
|
|
36
|
+
- Require status checks to pass before merging
|
|
37
|
+
- Disable force-pushes and branch deletion on the default branch
|
|
38
|
+
|
|
39
|
+
See the README "Configure branch protection" step for the exact `gh api` invocation. You **MUST NOT** proceed to treat the project as fully initialized while branch protection remains unconfigured without the user's explicit acknowledgment.
|
|
40
|
+
|
|
20
41
|
## Document Changelog Convention
|
|
21
42
|
|
|
22
43
|
Every document produced by this activity **MUST** include a **Changelog** table as the **first section** after the document title. The changelog tracks the version history of the document.
|
|
@@ -36,90 +57,119 @@ Every document produced by this activity **MUST** include a **Changelog** table
|
|
|
36
57
|
|
|
37
58
|
---
|
|
38
59
|
|
|
39
|
-
## Mode Detection
|
|
60
|
+
## Mode Detection
|
|
40
61
|
|
|
41
62
|
Before starting the interview, the skill **MUST** detect the repository mode and route accordingly. The detection logic is:
|
|
42
63
|
|
|
43
|
-
1. **
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
> **Precedence:** If both `component.json` AND `/docs` exist, multi-repo mode wins — `component.json` is the authoritative signal.
|
|
64
|
+
1. **Documented-repository mode:** `/docs` directory exists → interview + direct docs generation.
|
|
65
|
+
This mode is about whether documentation exists, not about how many packages the repository has. Repository _shape_ (single-package or monorepo) is detected separately — see Repository Shape Detection below. The mode was called "Mono-Repo" until `shared-understanding#D-44` renamed it to free the term.
|
|
66
|
+
2. **Undocumented / greenfield mode:** no `/docs` → investigation-first flow to bootstrap documentation from the codebase, then interview.
|
|
48
67
|
|
|
49
68
|
---
|
|
50
69
|
|
|
51
|
-
## Mode A —
|
|
70
|
+
## Mode A — Documented Repository (Current Flow)
|
|
52
71
|
|
|
53
|
-
When `
|
|
72
|
+
When `/docs` exists, the skill follows the **existing single-repo flow** unchanged.
|
|
54
73
|
|
|
55
74
|
### Process
|
|
56
75
|
|
|
57
|
-
1. **
|
|
58
|
-
2. **
|
|
76
|
+
1. **Receive Initial Brief:** The user describes the product, project, or technology stack.
|
|
77
|
+
2. **Ask Clarifying Questions:** Gather information for both product context and technical guidelines in a single interview. Group questions by domain.
|
|
78
|
+
3. **Generate Product Document:** Create `docs/product.md` using the structure below.
|
|
79
|
+
4. **Generate Technical Document:** Create `docs/tech.md` using the structure below.
|
|
80
|
+
5. **Save Output:** Save both documents in `/docs/` and present them for user review.
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
## Mode B — Undocumented / Greenfield
|
|
59
85
|
|
|
60
|
-
|
|
61
|
-
| --------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
62
|
-
| `0` | Success — bundle emitted | Load bundle files in numeric order. Present `review_flags` (if any) to the user before proceeding to planning. Continue to the interview for product context and technical guidelines using the bundle as input. |
|
|
63
|
-
| `7` | Gate abort — partition proposal | Present the partition proposal to the user. Explain that the scope is too broad and needs to be split. **Stop** — do not proceed to planning. |
|
|
64
|
-
| `9` | Stale catalog index | Inform the user that the catalog index is stale and needs to be rebuilt (e.g., `dt catalog build`). **Stop** — do not proceed. |
|
|
65
|
-
| `10` | Invalid scope after LLM retry | Inform the user that automatic scoping failed. Suggest running with `--components` for manual scope. **Stop.** |
|
|
66
|
-
| `11` | No candidates found | Inform the user that no components matched the task description. Suggest refining the task text or using `--components`. **Stop.** |
|
|
67
|
-
| `6` | Budget overflow | Inform the user that the scoped context exceeds the token budget. Suggest narrowing scope with `--max-components` or `--budget`. **Stop.** |
|
|
86
|
+
When `/docs` does not exist, the repository has no established documentation. The skill investigates the codebase directly before conducting the interview.
|
|
68
87
|
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
88
|
+
### Process
|
|
89
|
+
|
|
90
|
+
1. **Investigate the codebase:** Read manifest files (`package.json`, `pyproject.toml`, `go.mod`, or equivalent), the directory structure, the README, and any existing configuration to identify the technology stack, frameworks, and conventions in use.
|
|
91
|
+
2. **Present a findings summary:** Show the user what was found — stack, frameworks, notable directories, confidence per finding — before the interview.
|
|
92
|
+
3. **Conduct the interview:** Proceed with the standard clarifying questions for product and technical context (same as documented-repository mode).
|
|
93
|
+
4. **Generate documents:** Create `docs/product.md` and `docs/tech.md` using the investigation findings as pre-filled context combined with interview answers.
|
|
94
|
+
5. **Save Output:** Save both documents in `/docs/` and present them for user review.
|
|
73
95
|
|
|
74
96
|
### Constraints
|
|
75
97
|
|
|
76
|
-
- The
|
|
77
|
-
-
|
|
78
|
-
- The skill **MAY** ask follow-up questions to fill gaps not covered by the bundle (e.g., strategic goals, success metrics).
|
|
98
|
+
- The investigation findings inform but do not replace the interview — the user confirms and supplements.
|
|
99
|
+
- If the repository has no identifiable stack (an empty project), skip investigation and proceed directly to the interview (pure greenfield).
|
|
79
100
|
|
|
80
101
|
---
|
|
81
102
|
|
|
82
|
-
|
|
103
|
+
---
|
|
83
104
|
|
|
84
|
-
|
|
105
|
+
## Repository Shape Detection
|
|
85
106
|
|
|
86
|
-
|
|
107
|
+
Before the interview, detect the repository's **shape**. This is independent of the mode above: a documented repository can be either shape, and so can a greenfield one.
|
|
87
108
|
|
|
88
|
-
|
|
89
|
-
2. **Ask Clarifying Questions:** Gather information for both product context and technical guidelines in a single interview. Group questions by domain.
|
|
90
|
-
3. **Generate Product Context Document:** Create `product-context.md` using the structure below.
|
|
91
|
-
4. **Generate Technical Guidelines Document:** Create `technical-guidelines.md` using the structure below.
|
|
92
|
-
5. **Save Output:** Save both documents in `/docs/` and present them for user review.
|
|
109
|
+
Detect from these signals (FR-59):
|
|
93
110
|
|
|
94
|
-
|
|
111
|
+
| Signal | Read for |
|
|
112
|
+
| ----------------------------------------- | ------------------------------ |
|
|
113
|
+
| `pnpm-workspace.yaml` | Shape **and** the package list |
|
|
114
|
+
| `workspaces` in `package.json` | Shape **and** the package list |
|
|
115
|
+
| `turbo.json` | Shape only |
|
|
116
|
+
| `nx.json` | Shape only |
|
|
117
|
+
| `lerna.json` | Shape only |
|
|
118
|
+
| `[tool.uv.workspace]` in `pyproject.toml` | Shape only |
|
|
95
119
|
|
|
96
|
-
|
|
120
|
+
Any signal present → **monorepo**. No signal → **single-package**.
|
|
97
121
|
|
|
98
|
-
|
|
122
|
+
Only the first two are parsed for a package list. When a repository signals monorepo through one of the other four, ask the user which packages exist rather than guessing.
|
|
99
123
|
|
|
100
|
-
|
|
124
|
+
`core/distribution/workspace.ts` exports `detectWorkspace(repoRoot)`, which returns the shape, the signals found, and the packages. Use it rather than re-deriving the answer.
|
|
101
125
|
|
|
102
|
-
|
|
103
|
-
2. **Run extraction:** Invoke `dt extract all --interactive` to extract schema, OpenAPI, AsyncAPI, and component manifest from the codebase.
|
|
104
|
-
- The `--interactive` flag allows the user to confirm or skip ambiguous extractions.
|
|
105
|
-
- If interrupted, the skill **SHOULD** inform the user how to resume (`dt extract all --interactive` picks up where it left off).
|
|
106
|
-
3. **Present extraction report:** Show the user the results of extraction — what was found, confidence levels, any `unresolved` items.
|
|
107
|
-
4. **Conduct the interview:** Proceed with the standard clarifying questions for product context and technical guidelines (same as Mono-Repo mode).
|
|
108
|
-
5. **Generate documents:** Create `product-context.md` and `technical-guidelines.md` using the extraction results as pre-filled context combined with interview answers.
|
|
109
|
-
6. **Save Output:** Save both documents in `/docs/` and present them for user review.
|
|
126
|
+
### Package Map
|
|
110
127
|
|
|
111
|
-
|
|
128
|
+
Record the result in `docs/tech.md` as a **Package Map** section, one row per package:
|
|
129
|
+
|
|
130
|
+
```markdown
|
|
131
|
+
## Package Map
|
|
132
|
+
|
|
133
|
+
| Package | Path | Purpose | Owner | Canonical scripts | Bounded context |
|
|
134
|
+
| ---------- | ------------- | ------------------- | -------- | --------------------- | --------------- |
|
|
135
|
+
| @acme/core | packages/core | Shared domain logic | platform | lint, typecheck, test | Ordering |
|
|
136
|
+
```
|
|
112
137
|
|
|
113
|
-
|
|
114
|
-
|
|
138
|
+
Rules:
|
|
139
|
+
|
|
140
|
+
- A **single-package repository records exactly one row**, for the root, with path `.`. The table has the same shape in both cases, so a reader never has to work out which kind of repository they are looking at.
|
|
141
|
+
- **Purpose** and **Owner** come from the interview. Do not invent an owner; ask.
|
|
142
|
+
- **Canonical scripts** lists the scripts the package actually defines, in the order `lint`, `format:check`, `typecheck`, `test`, `test:unit`, `test:integration`, `test:e2e`, `audit`, `validate`. Absent scripts are omitted, not marked missing.
|
|
143
|
+
- **Bounded context** is filled **freeform at interview time** (`shared-understanding#D-45`). Ask: _"In one phrase, what part of the business or domain does this package own?"_ A freeform guess beats an empty column. Once `docs/domain/ubiquitous-language.md` defines a bounded context, that file is canonical: copy the name from its `## Bounded Context:` heading character for character, because `lint`'s glossary check matches the two exactly (`shared-understanding#D-69`, closing `#D-45`).
|
|
144
|
+
- A package whose `package.json` has no `name` is listed by its path. Do not invent a name — nothing would match it.
|
|
145
|
+
|
|
146
|
+
`dev-tasks doctor` warns when the map and the workspace disagree in either direction: a package on disk with no row, or a row for a package that no longer exists. It warns and never fails; structural failures belong to `lint`.
|
|
115
147
|
|
|
116
148
|
---
|
|
117
149
|
|
|
150
|
+
### Runbooks
|
|
151
|
+
|
|
152
|
+
Initialization also establishes `docs/runbooks/` (PRD AC-26, S-005 AC-7). Create:
|
|
153
|
+
|
|
154
|
+
- `docs/runbooks/README.md` — the index, with Runbook / Trigger / Owner / Last verified columns.
|
|
155
|
+
- `docs/runbooks/runbook-template.md` — the form to copy for a new procedure.
|
|
156
|
+
|
|
157
|
+
`dev-tasks install` delivers both install-if-absent, so in an installed repository they are already present and **MUST NOT** be overwritten. Create them only when absent, and confirm with the user which procedures are worth a runbook now rather than writing placeholder files.
|
|
158
|
+
|
|
159
|
+
## SIMPLICITY.md Confirmation
|
|
160
|
+
|
|
161
|
+
`SIMPLICITY.md` ships at the repository root and states the code-simplicity contract, including section D's tool-enforced thresholds. During initialization you **MUST** confirm two things with the user rather than assuming them:
|
|
162
|
+
|
|
163
|
+
1. **Owner** — who is accountable for the contract. The shipped default is `housekeeping`.
|
|
164
|
+
2. **Thresholds** — section D's defaults (function length ≤ 40 lines, cyclomatic complexity ≤ 10, cognitive complexity ≤ 15, nesting depth ≤ 3, parameters ≤ 4, file length ≤ 400 lines). A repository **MAY** tighten a default; it **MUST NOT** loosen one.
|
|
165
|
+
|
|
166
|
+
Ask: _"SIMPLICITY.md's owner is `housekeeping` and its thresholds are the shipped defaults. Keep both, or tighten anything?"_ Record the answer in the file's frontmatter and in the section D table. Wiring the thresholds into a linter is a separate procedure — see `docs/runbooks/runbook-setup-simplicity-tooling.md`.
|
|
167
|
+
|
|
118
168
|
## Part 1 — Product Context
|
|
119
169
|
|
|
120
170
|
### Clarifying Questions
|
|
121
171
|
|
|
122
|
-
Adapt questions based on context
|
|
172
|
+
Adapt questions based on context already gathered (e.g., from codebase investigation in greenfield mode):
|
|
123
173
|
|
|
124
174
|
- **Product Definition:** "What is this product/project, and what does it do?"
|
|
125
175
|
- **Problem Statement:** "What core problem does this product solve?"
|
|
@@ -132,7 +182,7 @@ Adapt questions based on context provided (and based on mode — in multi-repo m
|
|
|
132
182
|
- **Key Constraints:** "Budget, timeline, technology, or regulatory constraints?"
|
|
133
183
|
- **Stakeholders:** "Who are the key decision-makers?"
|
|
134
184
|
|
|
135
|
-
### Output Structure: `product
|
|
185
|
+
### Output Structure: `docs/product.md`
|
|
136
186
|
|
|
137
187
|
0. **Changelog** — Version history table (see Document Changelog Convention above)
|
|
138
188
|
1. **Executive Summary** — 2-3 sentence overview
|
|
@@ -171,27 +221,28 @@ Adapt questions based on context provided (and based on mode — in multi-repo m
|
|
|
171
221
|
- **Package Manager Standard:** "Can we standardize on `pnpm` for JS/TS projects?"
|
|
172
222
|
- **Script Naming Standard:** "Should canonical `package.json` scripts (`lint`, `format:check`, `typecheck`, `test`, `audit`, `validate`) be enforced?"
|
|
173
223
|
|
|
174
|
-
### Output Structure: `
|
|
224
|
+
### Output Structure: `docs/tech.md`
|
|
175
225
|
|
|
176
226
|
0. **Changelog** — Version history table (see Document Changelog Convention above)
|
|
177
227
|
1. **Overview** — Technical vision and guiding principles
|
|
178
|
-
2. **
|
|
179
|
-
3. **
|
|
180
|
-
4. **
|
|
181
|
-
5. **
|
|
182
|
-
6. **
|
|
183
|
-
7. **
|
|
184
|
-
8. **
|
|
185
|
-
9. **
|
|
186
|
-
10. **
|
|
187
|
-
11. **
|
|
188
|
-
12. **
|
|
189
|
-
13. **
|
|
190
|
-
14. **
|
|
191
|
-
15. **
|
|
192
|
-
16. **
|
|
193
|
-
17. **
|
|
194
|
-
18. **
|
|
228
|
+
2. **Package Map** — Repository shape and one row per package (see Repository Shape Detection above)
|
|
229
|
+
3. **Technology Stack** — Backend/frontend languages, frameworks, databases, key dependencies
|
|
230
|
+
4. **Architecture Patterns** — System architecture, key decisions and rationale, component organization
|
|
231
|
+
5. **API Design Standards** — Style, naming, request/response formats, error handling
|
|
232
|
+
6. **Authentication & Authorization** — Mechanism, model, permission levels, session management
|
|
233
|
+
7. **Security Requirements** — Encryption, OWASP compliance, API key management, PII handling
|
|
234
|
+
8. **Data & Database Guidelines** — Schema patterns, naming conventions, query optimization, backup
|
|
235
|
+
9. **Integration Methods** — External integrations, patterns, retry/failure handling
|
|
236
|
+
10. **Code Organization & Structure** — Folder/file conventions, module boundaries, naming
|
|
237
|
+
11. **Design Patterns & Principles** — Preferred patterns, SOLID, DRY/KISS/YAGNI
|
|
238
|
+
12. **Testing Strategy** — Frameworks, testing pyramid, coverage, mock strategies
|
|
239
|
+
13. **Code Quality & Standards** — Linting, static analysis, reviews, documentation
|
|
240
|
+
14. **Deployment & DevOps** — Environments, CI/CD, infrastructure-as-code, containers
|
|
241
|
+
15. **Monitoring, Logging & Observability** — Levels, frameworks, alerting, error tracking
|
|
242
|
+
16. **Performance & Scalability** — Response targets, throughput, caching, optimization
|
|
243
|
+
17. **Dependency Management** — Management approach, version pinning, vulnerability scanning
|
|
244
|
+
18. **Development Workflow** — Branching strategy, commit conventions, PR process
|
|
245
|
+
19. **Known Constraints & Trade-offs** — Limitations and rationale
|
|
195
246
|
|
|
196
247
|
### JS/TS Package Manager and Script Defaults
|
|
197
248
|
|
|
@@ -213,7 +264,7 @@ When the project includes JavaScript/TypeScript:
|
|
|
213
264
|
|
|
214
265
|
- **Format:** Markdown (`.md`)
|
|
215
266
|
- **Location:** `/docs/`
|
|
216
|
-
- **Filenames:** `product
|
|
267
|
+
- **Filenames:** `product.md`, `tech.md`
|
|
217
268
|
|
|
218
269
|
## AGENTS.md Sizing
|
|
219
270
|
|
|
@@ -232,4 +283,3 @@ When generating or updating `AGENTS.md` during project initialization, you **MUS
|
|
|
232
283
|
5. You **MUST** save both files and present them for user review.
|
|
233
284
|
6. You **SHOULD** iterate based on user feedback before finalizing.
|
|
234
285
|
7. When updating an existing document, you **MUST** add a new row to the Changelog table with an incremented version, the current date, a summary of changes, and the responsible author/agent.
|
|
235
|
-
8. In multi-repo mode, you **MUST NOT** read `/docs` or walk the repository directly — all context passes through `dt init`.
|