@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
|
@@ -28,26 +28,71 @@ This activity assumes:
|
|
|
28
28
|
|
|
29
29
|
---
|
|
30
30
|
|
|
31
|
+
## Package Scope in Commits
|
|
32
|
+
|
|
33
|
+
In a monorepo the package is the Conventional Commits **scope** (FR-63):
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
feat(api): add token-refresh endpoint
|
|
37
|
+
fix(web): stop double-submitting the checkout form
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
- Take the scope from the package map in `docs/tech.md`. Use the short,
|
|
41
|
+
readable form of the package name, not the full specifier: `@acme/api`
|
|
42
|
+
becomes `api`.
|
|
43
|
+
- A package name that is not a valid scope — one containing a space, a
|
|
44
|
+
slash after stripping the org prefix, or an uppercase letter — is
|
|
45
|
+
reduced to a lowercase, hyphenated form and the mapping is recorded in
|
|
46
|
+
the package map's row so every commit uses the same one. Never invent
|
|
47
|
+
a different short form per commit.
|
|
48
|
+
- A commit spanning packages uses the broadest honest scope, or none. A
|
|
49
|
+
scope that names one package for a change touching four is worse than
|
|
50
|
+
no scope.
|
|
51
|
+
- In a **single-package repository the scope is optional**. Omit it —
|
|
52
|
+
`feat: add the endpoint` — rather than writing an empty scope `feat():`,
|
|
53
|
+
which is not valid Conventional Commits and which the commit hook
|
|
54
|
+
rejects.
|
|
55
|
+
|
|
56
|
+
## Platform-Write Routing
|
|
57
|
+
|
|
58
|
+
- You **MUST NOT** emit or execute a platform write command (`aws`, `flyctl`, `supabase`, or Cloudflare API writes) while executing a task list.
|
|
59
|
+
- When a sub-task's work is a platform write, you **MUST** route it to `infra-engineer` instead of running it yourself, so the approval, revert, and backup gates bind. The sub-task kinds that route are: **secrets**, **deploy**, **DNS**, **certificates**, **IAM policy**, and **migrations against a shared or cloud project**.
|
|
60
|
+
- This routing is **conditional**, never mandatory: a story with no platform-write scope invokes nothing, and an infra-shaped but local-only sub-task — such as editing `.env.example` or a config template checked into the repo — stays with the implementing agent.
|
|
61
|
+
|
|
62
|
+
---
|
|
63
|
+
|
|
31
64
|
## Before Starting Work
|
|
32
65
|
|
|
33
66
|
1. You **MUST** confirm the GitHub Issue is open.
|
|
34
|
-
2. **
|
|
67
|
+
2. **Decision-log read (non-mutating — runs before any branch is created):** You **MUST** read `workstream/decisions-<feature>.md` in full, alongside (not replacing) the GitHub-issue-open check in step 1 — both checks run before branch creation. This step is ordered before the branch gate (step 3) precisely because it is non-mutating: reading it first lets you answer your own procedural questions (e.g., "was this file's location already decided?") from the log before touching git. If `workstream/decisions-<feature>.md` does not exist — for example, a pre-Phase-2 feature, or a feature for which grilling never ran — you **MUST** proceed without the read, noting its absence in your status output, rather than failing or blocking. This is an enrichment, never a hard gate: a missing decision log never blocks starting work. A decision log that exists but has zero rows is treated the same as present-and-populated — there is simply nothing to cite.
|
|
68
|
+
3. **Branch gate (hard requirement):** You **MUST** verify you are on a feature branch before any implementation work:
|
|
35
69
|
- Run `git rev-parse --abbrev-ref HEAD` to determine the current branch.
|
|
36
70
|
- If HEAD is the default branch (`main`) or does not match `issue/*` or `story/*` pattern, you **MUST** create a new branch from the latest default branch by delegating branch naming and creation to `github-ops` whenever possible.
|
|
37
71
|
- You **MUST NOT** proceed with any implementation sub-task, write any code, create any files, or make any commits until a feature branch is checked out.
|
|
38
|
-
- If HEAD is already a valid feature branch (matching `issue/*` or `story/*`), proceed to step
|
|
72
|
+
- If HEAD is already a valid feature branch (matching `issue/*` or `story/*`), proceed to step 4.
|
|
39
73
|
- Branch format: `issue/<issue-number>-<short-description>` or `story/<id>-<short-description>`
|
|
40
|
-
|
|
74
|
+
4. You **MUST** open a **draft Pull Request** by delegating to `github-ops` whenever possible.
|
|
41
75
|
- A PR requires at least one commit. Open it immediately after the first commit on the feature branch — never before — and you **MUST NOT** continue past that first commit without it.
|
|
42
76
|
- Base branch is the default branch unless an orchestrating caller explicitly provides a base-branch override.
|
|
43
77
|
- PR title **MUST** follow Conventional Commits (e.g., `feat: implement issue 37`).
|
|
44
78
|
- PR description **MUST** include `Closes #<issue-number>`.
|
|
45
|
-
|
|
79
|
+
5. You **MUST** ensure the task list in the GitHub Issue matches the local `/workstream/tasks-*.md` file.
|
|
46
80
|
|
|
47
81
|
If `github-ops` delegation is unavailable in the current runtime, you **MUST** apply `github-ops` conventions directly and explicitly note that fallback in your status output.
|
|
48
82
|
|
|
49
83
|
---
|
|
50
84
|
|
|
85
|
+
## Decision-Log Citation
|
|
86
|
+
|
|
87
|
+
When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
88
|
+
|
|
89
|
+
- An implementation commit whose approach was shaped by a decision **MUST** cite it in the commit body — e.g. a trailing line `Follows D-NN: <short form>.` — using the feature's own unqualified `D-NN` form (the file belongs to one feature; the qualified `<feature>#D-NN` cross-file form is `activity-grill`/`activity-refine`/`activity-generate-spec`'s concern, not `implement`'s).
|
|
90
|
+
- The PR body **MUST** reference every consumed decision ID it draws on, in its Completion Report area, alongside the existing `Closes #<issue-number>` line.
|
|
91
|
+
- This is **additive only**, mirroring `plan`'s own citation contract: a commit or PR with no traceable decision cites none. You **MUST NOT** fabricate a citation to give a commit or PR one.
|
|
92
|
+
- When step 2 found no `workstream/decisions-<feature>.md` (absent or empty), there is nothing to cite — omit the citation, do not fabricate one, and do not treat the omission as a defect.
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
51
96
|
## During Implementation
|
|
52
97
|
|
|
53
98
|
### Step-by-Step Execution
|
|
@@ -64,7 +64,7 @@ The task list **MUST** follow this structure:
|
|
|
64
64
|
|
|
65
65
|
- [ ] 1.0 Implement Story [ID]: [Story Title] (or: Implement Issue [#] - [Github_Issue_URL]: [Title])
|
|
66
66
|
|
|
67
|
-
- [ ] 1.1 [First implementation step]
|
|
67
|
+
- [ ] 1.1 [First implementation step] (D-NN, when traceable — omit otherwise)
|
|
68
68
|
- [ ] 1.2 [Second implementation step]
|
|
69
69
|
- [ ] 1.x Verify Acceptance Criterion: [Criterion 1]
|
|
70
70
|
- [ ] 1.y Verify Acceptance Criterion: [Criterion 2]
|
|
@@ -73,8 +73,48 @@ The task list **MUST** follow this structure:
|
|
|
73
73
|
- [ ] 2.0 Implement Story [ID]: [Story Title] (or: Implement Issue [#] - [Github_Issue_URL]: [Title])
|
|
74
74
|
- [ ] 2.1 [First implementation step]
|
|
75
75
|
- ...
|
|
76
|
+
|
|
77
|
+
## Decisions Consumed
|
|
78
|
+
|
|
79
|
+
| ID | Decision (short form) |
|
|
80
|
+
| ---- | --------------------- |
|
|
81
|
+
| D-NN | … |
|
|
76
82
|
```
|
|
77
83
|
|
|
84
|
+
## Decision Citations
|
|
85
|
+
|
|
86
|
+
A task line that derives from a specific decision cites it inline, at the
|
|
87
|
+
end of the line: `- [ ] 3.2 Add cap-reached prompt (D-55)` (FR-16).
|
|
88
|
+
|
|
89
|
+
- Citations reference the feature's own `decisions-<feature>.md` by
|
|
90
|
+
unqualified `D-NN` — a task list belongs to exactly one feature, so the
|
|
91
|
+
qualified `<feature>#D-NN` form `activity-refine`/`activity-generate-spec`
|
|
92
|
+
use for cross-feature reuse is never needed here.
|
|
93
|
+
- This is **additive only**: a task with no traceable decision cites none.
|
|
94
|
+
You **MUST NOT** fabricate a citation to give a task one.
|
|
95
|
+
- The task list closes with a `## Decisions Consumed` section aggregating
|
|
96
|
+
every decision ID cited anywhere in the list, in the same `ID | Decision
|
|
97
|
+
(short form)` table shape the decision log itself uses. A task list that
|
|
98
|
+
cites no decisions still includes the section, empty (header plus
|
|
99
|
+
table skeleton, no rows) — consistent with how `activity-refine`'s and
|
|
100
|
+
`activity-generate-spec`'s own `## Decisions` sections may legitimately
|
|
101
|
+
be empty.
|
|
102
|
+
|
|
103
|
+
## Package Attribution
|
|
104
|
+
|
|
105
|
+
Every task **MUST** name the package it changes (FR-63), so a reader can
|
|
106
|
+
tell the blast radius from the task list without opening the diff.
|
|
107
|
+
|
|
108
|
+
- Read the package map in `docs/tech.md` for the package list.
|
|
109
|
+
- Write the package in the sub-task text, in brackets, first:
|
|
110
|
+
`- [ ] 1.1 [@acme/api] Add the token-refresh endpoint`.
|
|
111
|
+
- A sub-task touching several packages lists them all. A sub-task that
|
|
112
|
+
touches _most_ packages is usually the wrong size — split it.
|
|
113
|
+
- In a **single-package repository the bracket is omitted**, not left
|
|
114
|
+
empty. It is optional there, never blank.
|
|
115
|
+
- Non-code tasks (docs, workflow files) that belong to no package use
|
|
116
|
+
`[repo root]`.
|
|
117
|
+
|
|
78
118
|
## Conversion Guidelines
|
|
79
119
|
|
|
80
120
|
When converting a **User Story** or **Refined Issue** to a **Parent Task**:
|
|
@@ -93,6 +133,7 @@ When converting a **User Story** or **Refined Issue** to a **Parent Task**:
|
|
|
93
133
|
- If schema or data-model changes are involved, migration tasks are **required by default**; omission is allowed only with an explicit documented opt-out rationale.
|
|
94
134
|
- Migration flows **MUST** include: create migration artifact, document rollback/impact, request user confirmation before apply, apply migration after confirmation, and verify applied state.
|
|
95
135
|
- If the story involves data models, you **SHOULD** include a sub-task to generate seed data.
|
|
136
|
+
- When `workstream/decisions-<feature>.md` exists, you **MUST** cite the decision ID inline (`… (D-NN)`) on any sub-task whose approach or scope traces to a specific decision row, and **MUST** populate the closing `## Decisions Consumed` section with every ID cited anywhere in the list. This is additive only — a sub-task with no traceable decision cites none; do not fabricate a citation.
|
|
96
137
|
|
|
97
138
|
3. **Context:** You **MAY** add a `> Note:` block under the parent task for quick reference (User Story text or Business Rules), but the checkbox structure **MUST** remain clean.
|
|
98
139
|
4. **Relevant Files:** You **MUST** aggregate all "Files to Create/Modify" from selected stories into the top-level `Relevant Files` section.
|
|
@@ -138,6 +179,7 @@ If this is a **greenfield project** or a **new component**, you **MUST** include
|
|
|
138
179
|
5. You **MUST** ensure all Implementation Steps, Acceptance Criteria, and Testing requirements are preserved as sub-tasks.
|
|
139
180
|
6. For JS/TS repositories, you **MUST** prefer `pnpm` commands and canonical script names in generated tasks.
|
|
140
181
|
7. You **MUST** ensure each task includes both implementation and test/validation steps, including edge-case validation.
|
|
182
|
+
7a. When a decision log exists for the feature, you **MUST** cite the decision ID inline on any traceable sub-task and populate the closing `## Decisions Consumed` section (FR-16) — additively, never fabricated.
|
|
141
183
|
8. For schema/data-model changes, you **MUST** include migration lifecycle tasks and an explicit user-confirmation gate before applying migrations unless an opt-out rationale is documented.
|
|
142
184
|
9. You **MUST** update the corresponding GitHub Issue(s) with the task checklist by delegating to `github-ops` whenever possible. If no issue exists, you **MUST** ask the user whether to create one first.
|
|
143
185
|
10. You **MUST** save the task list file.
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
---
|
|
2
|
+
agent: infra-engineer
|
|
3
|
+
description: "Plan infrastructure changes as approved, reversible steps and record the result for a draft PR handoff."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
Run the `infra-engineer` agent for an infrastructure change.
|
|
7
|
+
|
|
8
|
+
- **Request:** `<environment and change request>`
|
|
9
|
+
- **Environment file:** `infra/environments.yaml`
|
|
10
|
+
- **Record root:** `infra/changes/<YYYYMMDD>-<ChangeId>/`
|
|
11
|
+
|
|
12
|
+
The agent must use the complete infra-engineer contract: discover → plan → approve plan → one approved step at a time with backup, apply, verify, and record. It blocks template-status environments, identity mismatches, missing tools or version floors, missing production backup/revert, foundation writes, unbounded log queries, and unapproved changes. It never creates or pushes tags or pushes/merges to `main`.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
agent: product-engineer
|
|
3
|
-
description: "Initialize project foundation — create product
|
|
3
|
+
description: "Initialize project foundation — create product.md and tech.md."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
Run the `product-engineer` agent to establish foundation documents for this project:
|
|
@@ -10,13 +10,12 @@ Run the `product-engineer` agent to establish foundation documents for this proj
|
|
|
10
10
|
|
|
11
11
|
The agent will invoke the `activity-init` skill which first **detects the repository mode**:
|
|
12
12
|
|
|
13
|
-
- **
|
|
14
|
-
- **
|
|
15
|
-
- **Undocumented/greenfield** (neither): runs `dt extract detect` → `dt extract all --interactive` → interview
|
|
13
|
+
- **Documented repository** (`/docs` present): standard interview flow
|
|
14
|
+
- **Undocumented/greenfield** (`/docs` absent): investigates the codebase directly, then interview
|
|
16
15
|
|
|
17
16
|
Then creates:
|
|
18
17
|
|
|
19
|
-
- `docs/product
|
|
20
|
-
- `docs/
|
|
18
|
+
- `docs/product.md` — Product context and strategic goals
|
|
19
|
+
- `docs/tech.md` — Technical standards and patterns
|
|
21
20
|
|
|
22
21
|
These documents serve as the "constitution" for all future development. Run this once per project or on major strategic/technical pivots.
|
|
@@ -11,11 +11,10 @@ Run the `researcher` agent for a codebase investigation.
|
|
|
11
11
|
The agent runs one procedure:
|
|
12
12
|
|
|
13
13
|
1. **Intake** — receives the research question; asks one clarification if vague.
|
|
14
|
-
2. **
|
|
15
|
-
3. **
|
|
16
|
-
4. **
|
|
17
|
-
5. **
|
|
18
|
-
6. **Provenance** — records repository, branch, commit SHA, date; consumers treat the artifact as stale when HEAD advances.
|
|
14
|
+
2. **Slice execution** — investigates all eight slices: S1 Components/modules, S2 APIs/contracts, S3 UI surfaces, S4 Tests, S5 Data model, S6 Config/env/CI, S7 Relationships, S8 Prior history.
|
|
15
|
+
3. **Synthesis** — writes answer-first summary, compiles relevance-ranked file map, derives relationships, risks, and gaps.
|
|
16
|
+
4. **Budget enforcement** — ensures report <= 250 lines and <= 30 cited files.
|
|
17
|
+
5. **Provenance** — records repository, branch, commit SHA, date; consumers treat the artifact as stale when HEAD advances.
|
|
19
18
|
|
|
20
19
|
The agent will **not**:
|
|
21
20
|
|
|
@@ -14,7 +14,7 @@ Context for this pass _(provide one or more)_:
|
|
|
14
14
|
The agent will:
|
|
15
15
|
|
|
16
16
|
- Update `/docs` artifacts to reflect current implemented behavior
|
|
17
|
-
- Create a new ADR in `/docs/adr/` if `
|
|
17
|
+
- Create a new ADR in `/docs/adr/` if `tech.md` changed
|
|
18
18
|
- Update `/docs/user-guide/` for any user-visible changes
|
|
19
19
|
- Keep `mkdocs.yml` navigation in sync with pages on disk
|
|
20
20
|
|
|
@@ -1,8 +1,3 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: activity-codebase-research
|
|
3
|
-
description: "Perform bounded, delegated codebase investigation and emit a structured research artifact. Use when downstream agents need grounded, file-level evidence without pulling the search transcript into their own context."
|
|
4
|
-
---
|
|
5
|
-
|
|
6
1
|
# Activity: Codebase Research
|
|
7
2
|
|
|
8
3
|
Investigate a bounded research question against the current codebase and produce one structured artifact (`/workstream/research-*.md`). The artifact replaces an ad-hoc exploratory reading session — the search transcript is discarded and only the report survives.
|
|
@@ -80,13 +75,7 @@ The artifact **MUST** contain exactly these ten sections, in this order:
|
|
|
80
75
|
2. If the question is vague or spans more than one answerable topic, ask **one** focused clarification. Do not proceed with an unfocused survey.
|
|
81
76
|
3. Identify the target scope: files, directories, modules, or packages likely relevant.
|
|
82
77
|
|
|
83
|
-
### Phase 2 —
|
|
84
|
-
|
|
85
|
-
1. Check for `component.json` in the repository root.
|
|
86
|
-
2. **If present:** Consume `dt context` / `dt catalog` output to identify cross-repo boundaries, dependencies, and contracts. Cite catalog output as a source in Provenance.
|
|
87
|
-
3. **If absent or `dt` unavailable:** Fall back to direct file scanning (grep, tree-sitter, file search). Record the fallback in Provenance — never fail outright.
|
|
88
|
-
|
|
89
|
-
### Phase 3 — Slice Execution
|
|
78
|
+
### Phase 2 — Slice Execution
|
|
90
79
|
|
|
91
80
|
For each of the eight slices (S1-S8):
|
|
92
81
|
|
|
@@ -95,7 +84,7 @@ For each of the eight slices (S1-S8):
|
|
|
95
84
|
3. If no evidence exists for a slice, mark it `N/A` with a reason (e.g., "No UI surfaces exist in this area").
|
|
96
85
|
4. Rank findings by relevance to the research question, not alphabetically.
|
|
97
86
|
|
|
98
|
-
### Phase
|
|
87
|
+
### Phase 3 — Synthesis
|
|
99
88
|
|
|
100
89
|
1. Write the **Answer first** section: directly answer the research question in <= 10 lines using the evidence gathered.
|
|
101
90
|
2. Compile the **Relevance-ranked file map** from the top findings across all slices (max 30 files).
|
|
@@ -105,13 +94,13 @@ For each of the eight slices (S1-S8):
|
|
|
105
94
|
6. Populate **Not investigated** with areas deliberately skipped (out of scope, budget exhausted, tooling unavailable).
|
|
106
95
|
7. Assign a **Confidence** level based on coverage completeness, source quality, and known gaps.
|
|
107
96
|
|
|
108
|
-
### Phase
|
|
97
|
+
### Phase 4 — Budget Enforcement
|
|
109
98
|
|
|
110
99
|
1. Count report lines. If > 250, remove the lowest-relevance findings until compliant and record omissions under "Not Investigated".
|
|
111
100
|
2. Count cited files. If > 30, collapse the lowest-relevance entries and record omissions.
|
|
112
101
|
3. Final check: all ten sections present and in order; all eight slices addressed; both caps satisfied.
|
|
113
102
|
|
|
114
|
-
### Phase
|
|
103
|
+
### Phase 5 — Provenance and Output
|
|
115
104
|
|
|
116
105
|
1. Record in Provenance:
|
|
117
106
|
- Repository name
|
|
@@ -120,7 +109,6 @@ For each of the eight slices (S1-S8):
|
|
|
120
109
|
- Invoking agent (e.g., `product-engineer`, `developer`, `planner`)
|
|
121
110
|
- Research question (verbatim)
|
|
122
111
|
- Date (ISO 8601)
|
|
123
|
-
- Multi-repo source: `dt context` or `direct scanning (fallback)`
|
|
124
112
|
2. Write the artifact to the contract path.
|
|
125
113
|
3. Optionally post a one-line summary as a GitHub issue comment.
|
|
126
114
|
|
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
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.
|
|
4
4
|
|
|
5
|
+
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).
|
|
6
|
+
|
|
5
7
|
---
|
|
6
8
|
|
|
7
9
|
> **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).
|
|
@@ -14,8 +16,8 @@ Transform refined requirements (PRD) into an actionable technical design by synt
|
|
|
14
16
|
|
|
15
17
|
This activity assumes the following documents already exist:
|
|
16
18
|
|
|
17
|
-
- `product
|
|
18
|
-
- `
|
|
19
|
+
- `product.md` — Product understanding
|
|
20
|
+
- `tech.md` — Technical standards and patterns
|
|
19
21
|
- `prd-[feature-name].md` — Feature requirements (produced by the **refine** activity)
|
|
20
22
|
|
|
21
23
|
## Document Changelog Convention
|
|
@@ -37,13 +39,13 @@ Every specification produced by this activity **MUST** include a **Changelog** t
|
|
|
37
39
|
|
|
38
40
|
## Process
|
|
39
41
|
|
|
40
|
-
1. **Receive References:** User points to the existing PRD and confirms Technical Guidelines are available.
|
|
42
|
+
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.
|
|
41
43
|
2. **Analyze Documents:** You **MUST** read and analyze both the PRD and Technical Guidelines to identify integration points.
|
|
42
|
-
3. **
|
|
43
|
-
4. **Generate Specification:** You **MUST** create a comprehensive technical specification using the structure below.
|
|
44
|
+
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.
|
|
45
|
+
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.
|
|
44
46
|
5. **Save Output.**
|
|
45
47
|
|
|
46
|
-
##
|
|
48
|
+
## Candidate Specification Questions (seed the `activity-grill` interview)
|
|
47
49
|
|
|
48
50
|
Focus on technical decisions and implementation approach:
|
|
49
51
|
|
|
@@ -82,6 +84,26 @@ The generated Specification document **MUST** include:
|
|
|
82
84
|
15. **Deployment & Rollout** — Feature flags, migration steps, backward compatibility, rollback plan
|
|
83
85
|
16. **Dependencies & Risks** — Technology dependencies, known risks, mitigation strategies
|
|
84
86
|
17. **Open Questions** — Remaining technical decisions
|
|
87
|
+
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
|
|
88
|
+
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
|
|
89
|
+
|
|
90
|
+
## Vocabulary Section (FR-20, D-61, D-75)
|
|
91
|
+
|
|
92
|
+
The specification carries a `## Vocabulary` section immediately after `## Decisions (HOW phase)`, in the same shape `activity-refine` uses for PRDs:
|
|
93
|
+
|
|
94
|
+
```markdown
|
|
95
|
+
## Vocabulary
|
|
96
|
+
|
|
97
|
+
| Term | Status in glossary | Bounded context | Definition (proposals only) | Forbidden synonyms (proposals only) |
|
|
98
|
+
| ---- | --------------------------------------- | --------------- | --------------------------- | ----------------------------------- |
|
|
99
|
+
| … | existing \| proposed \| conflict → D-NN | … | … | … |
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
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.`
|
|
103
|
+
|
|
104
|
+
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).
|
|
105
|
+
|
|
106
|
+
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.
|
|
85
107
|
|
|
86
108
|
## Diagram Guidelines
|
|
87
109
|
|
|
@@ -125,8 +147,10 @@ The specification **MUST** clearly show how:
|
|
|
125
147
|
|
|
126
148
|
1. You **MUST NOT** start implementing.
|
|
127
149
|
2. You **MUST** read the referenced PRD and Technical Guidelines documents.
|
|
128
|
-
3. You **
|
|
150
|
+
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).
|
|
129
151
|
4. You **MUST** ensure the specification clearly maps PRD requirements to technical solutions.
|
|
130
|
-
5.
|
|
131
|
-
6. You **MUST**
|
|
132
|
-
7.
|
|
152
|
+
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).
|
|
153
|
+
6. You **MUST** present the specification for user review.
|
|
154
|
+
7. You **MUST** save the finalized version.
|
|
155
|
+
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.
|
|
156
|
+
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,145 @@
|
|
|
1
|
+
# Activity: Grill
|
|
2
|
+
|
|
3
|
+
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.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
> **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).
|
|
8
|
+
|
|
9
|
+
## Goal
|
|
10
|
+
|
|
11
|
+
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.
|
|
12
|
+
|
|
13
|
+
## Invocation
|
|
14
|
+
|
|
15
|
+
The caller passes:
|
|
16
|
+
|
|
17
|
+
- `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).
|
|
18
|
+
- `cap` — the question cap for this phase (see Cap Configuration below).
|
|
19
|
+
- `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.
|
|
20
|
+
- `feature` — the slug used to name `workstream/decisions-<feature>.md`.
|
|
21
|
+
|
|
22
|
+
## Context
|
|
23
|
+
|
|
24
|
+
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.
|
|
25
|
+
|
|
26
|
+
## Write Authority
|
|
27
|
+
|
|
28
|
+
- `workstream/decisions-<feature>.md` — append one row per resolved question, immediately (FR-4). Never batch writes to the end of a session.
|
|
29
|
+
- Nothing else. No PRD, spec, task list, code, or `/DESIGN.md` file may be created or modified by this skill.
|
|
30
|
+
|
|
31
|
+
## Process
|
|
32
|
+
|
|
33
|
+
### 1. One question, one recommendation, per turn (FR-1)
|
|
34
|
+
|
|
35
|
+
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.
|
|
36
|
+
|
|
37
|
+
### 2. Depth-first traversal (FR-2)
|
|
38
|
+
|
|
39
|
+
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.
|
|
40
|
+
|
|
41
|
+
### 3. Resolve-before-ask (FR-3)
|
|
42
|
+
|
|
43
|
+
Before asking the user anything, check in this order:
|
|
44
|
+
|
|
45
|
+
1. **Codebase directly** — `Read`/`Grep`/`Glob` for single-file questions (e.g., "does this config already exist?").
|
|
46
|
+
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).
|
|
47
|
+
3. **Prior `decisions-*.md` files** for a matching answer — mandatory in Issue Mode (FR-10), optional-but-recommended in Feature Mode.
|
|
48
|
+
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.
|
|
49
|
+
|
|
50
|
+
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.
|
|
51
|
+
|
|
52
|
+
### 3a. Vocabulary conflicts are questions, never resolutions (FR-21)
|
|
53
|
+
|
|
54
|
+
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.
|
|
55
|
+
|
|
56
|
+
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:
|
|
57
|
+
|
|
58
|
+
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.
|
|
59
|
+
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.
|
|
60
|
+
|
|
61
|
+
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.
|
|
62
|
+
|
|
63
|
+
Two cases resolve without a new question, or with one question rather than several:
|
|
64
|
+
|
|
65
|
+
- **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.
|
|
66
|
+
- **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).
|
|
67
|
+
|
|
68
|
+
The skill reads the glossary and writes nothing to it, in every mode and every phase — see Write Authority.
|
|
69
|
+
|
|
70
|
+
### 4. Append-per-resolution (FR-4)
|
|
71
|
+
|
|
72
|
+
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.
|
|
73
|
+
|
|
74
|
+
### 5. Qualified citation form (FR-5)
|
|
75
|
+
|
|
76
|
+
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.
|
|
77
|
+
|
|
78
|
+
### 6. Decision-tree summary cadence (FR-6)
|
|
79
|
+
|
|
80
|
+
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.
|
|
81
|
+
|
|
82
|
+
### 7. Two-phase mode (FR-7)
|
|
83
|
+
|
|
84
|
+
`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.
|
|
85
|
+
|
|
86
|
+
### 8. Hard exit gate (FR-8)
|
|
87
|
+
|
|
88
|
+
The exit gate is satisfied only when **both** hold:
|
|
89
|
+
|
|
90
|
+
- The open-questions list is empty, **and**
|
|
91
|
+
- The user has made an explicit statement of shared understanding (e.g., "I understand, proceed" / "I confirm").
|
|
92
|
+
|
|
93
|
+
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.
|
|
94
|
+
|
|
95
|
+
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.
|
|
96
|
+
|
|
97
|
+
### 9. Configurable, enforced cap (FR-9)
|
|
98
|
+
|
|
99
|
+
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.
|
|
100
|
+
|
|
101
|
+
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.
|
|
102
|
+
|
|
103
|
+
### 10. Issue Mode constraints (FR-10)
|
|
104
|
+
|
|
105
|
+
When `mode="issue"`:
|
|
106
|
+
|
|
107
|
+
- **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.
|
|
108
|
+
- **Scope is limited** to what the issue changes relative to current behavior — do not open branches outside that delta.
|
|
109
|
+
- **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.
|
|
110
|
+
- The cap is 8, per the default above (or the configured `docs/tech.md` § Grilling issue-mode value).
|
|
111
|
+
|
|
112
|
+
### 11. Assumption-testing reminder (FR-11, SHOULD)
|
|
113
|
+
|
|
114
|
+
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.
|
|
115
|
+
|
|
116
|
+
## Cap Configuration
|
|
117
|
+
|
|
118
|
+
| Mode | Default cap | Configured source |
|
|
119
|
+
| ------------------ | ----------- | ------------------------------------- |
|
|
120
|
+
| Feature Mode, WHAT | 25 | `docs/tech.md` § Grilling, if present |
|
|
121
|
+
| Feature Mode, HOW | 25 | `docs/tech.md` § Grilling, if present |
|
|
122
|
+
| Issue Mode | 8 | `docs/tech.md` § Grilling, if present |
|
|
123
|
+
|
|
124
|
+
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).
|
|
125
|
+
|
|
126
|
+
## Session State (D-54)
|
|
127
|
+
|
|
128
|
+
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.
|
|
129
|
+
|
|
130
|
+
## Attribution (D-53)
|
|
131
|
+
|
|
132
|
+
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.
|
|
133
|
+
|
|
134
|
+
## Output
|
|
135
|
+
|
|
136
|
+
- Zero or more new rows appended to `workstream/decisions-<feature>.md`, one per resolved question, written as each question resolves.
|
|
137
|
+
- A returned exit-gate status to the caller: satisfied (open list empty and explicit confirmation received) or not yet satisfied.
|
|
138
|
+
- Zero or more decision-tree summaries printed to the conversation at the required cadence (every 10th resolution, cap, exit attempt).
|
|
139
|
+
|
|
140
|
+
## Non-Goals
|
|
141
|
+
|
|
142
|
+
- Not a drafting skill — produces no PRD, spec, or task-list content itself.
|
|
143
|
+
- Not a top-level entry point — only `activity-refine` and `activity-generate-spec` invoke it.
|
|
144
|
+
- 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).
|
|
145
|
+
- Not a second, independent `researcher` budget — shares the phase's existing conditional pre-step budget (D-56, ADR-004).
|