@llipe.com/dev-tasks 0.11.0 → 0.16.2
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 +138 -62
- 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 +64 -7
- package/.claude/agents/ux-engineer.md +1 -0
- package/.claude/agents/verifier.md +63 -6
- package/.claude/commands/developer.md +2 -266
- package/.claude/commands/infra-engineer.md +92 -0
- package/.claude/commands/planner.md +98 -29
- package/.claude/commands/product-engineer.md +69 -11
- 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 +573 -24
- 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 +61 -12
- package/.claude/skills/memo-cli-usage/REFERENCE.md +230 -17
- package/.claude/skills/memo-cli-usage/SKILL.md +68 -13
- package/.claude/skills/plan/SKILL.md +43 -1
- package/.claude/skills/supabase-ops/SKILL.md +109 -0
- package/.github/agents/developer.agent.md +103 -38
- 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 +79 -10
- package/.github/agents/product-engineer.agent.md +69 -11
- package/.github/agents/qa-engineer.agent.md +23 -11
- package/.github/agents/researcher.agent.md +25 -6
- package/.github/agents/technical-writer.agent.md +63 -7
- package/.github/agents/verifier.agent.md +61 -5
- package/.github/instructions/implement.instructions.md +61 -12
- 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 +68 -13
- package/.github/skills/supabase-ops/SKILL.md +104 -0
- package/.kiro/agents/developer.md +104 -39
- 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 +87 -21
- package/.kiro/agents/product-engineer.md +72 -14
- package/.kiro/agents/qa-engineer.md +24 -12
- package/.kiro/agents/researcher.md +26 -7
- package/.kiro/agents/technical-writer.md +66 -10
- package/.kiro/agents/verifier.md +62 -6
- package/.kiro/hooks/scripts/git-guard.sh +96 -10
- 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 +68 -13
- package/.kiro/skills/supabase-ops/SKILL.md +109 -0
- package/.kiro/steering/implement.md +61 -12
- package/.kiro/steering/plan.md +43 -1
- package/AGENTS.md +67 -114
- package/AGENTS.md.template +126 -0
- package/CHANGELOG.md +182 -0
- package/CLAUDE.md +25 -19
- package/CLAUDE.md.template +104 -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
package/.kiro/agents/verifier.md
CHANGED
|
@@ -3,7 +3,7 @@ description: "Verification agent that owns both compliance test-plan design and
|
|
|
3
3
|
tools: [read, write, shell]
|
|
4
4
|
resources:
|
|
5
5
|
- file://AGENTS.md
|
|
6
|
-
- file://docs/
|
|
6
|
+
- file://docs/tech.md
|
|
7
7
|
- skill://.kiro/skills/**/SKILL.md
|
|
8
8
|
---
|
|
9
9
|
|
|
@@ -169,11 +169,11 @@ Execution follows a strict phase-gated flow. You **MUST NOT** advance to the nex
|
|
|
169
169
|
|
|
170
170
|
**Audit Mode:**
|
|
171
171
|
|
|
172
|
-
| |
|
|
173
|
-
| ------------------ |
|
|
174
|
-
| **Entry criteria** | Phase 2 complete.
|
|
175
|
-
| **Actions** | Read the codebase implementation (diff/PR/branch), `/workstream` artifacts, and the test suite. Execute or observe test results against delivered code. Collect per-AC evidence (pass/fail/drift). Classify every drift item by impact and intent. |
|
|
176
|
-
| **Exit criteria** | Evidence collected for every AC against all four sources (codebase, `/workstream`, tests, PRD/spec intent). Every drift item classified.
|
|
172
|
+
| | |
|
|
173
|
+
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
174
|
+
| **Entry criteria** | Phase 2 complete. |
|
|
175
|
+
| **Actions** | Read the codebase implementation (diff/PR/branch), `/workstream` artifacts, and the test suite. Execute or observe test results against delivered code. Collect per-AC evidence (pass/fail/drift). Classify every drift item by impact and intent. Run the docs-structure check for the documentation section of the report: `tsx core/checks/run.ts`, or `checkDocsStructure(repoRoot)` from `core/checks` directly. Report its findings; do **not** re-derive them by reading indexes and runbooks by hand. One implementation, two callers — `lint` enforces, this audit reports. Run the vocabulary conformance scan the same way: `checkExportedIdentifiers(addedLines, glossaryMarkdown)` from `core/checks`, where `addedLines` are the added (`+`) lines of `git diff <base>...HEAD` and `glossaryMarkdown` is `docs/domain/ubiquitous-language.md`. Its hits are **advisory** and **never block** PR readiness in this release (D-63). |
|
|
176
|
+
| **Exit criteria** | Evidence collected for every AC against all four sources (codebase, `/workstream`, tests, PRD/spec intent). Every drift item classified. |
|
|
177
177
|
|
|
178
178
|
### Phase 4 — Reporting & Publication
|
|
179
179
|
|
|
@@ -210,6 +210,60 @@ Execution follows a strict phase-gated flow. You **MUST NOT** advance to the nex
|
|
|
210
210
|
13. **No false completion:** If traceability or audit coverage is incomplete, you **MUST** mark status as `blocked` and list missing evidence.
|
|
211
211
|
14. **No direct edits:** You **MUST NOT** edit application code, PRD, spec, or task-list content — you report findings and hand off remediation to `developer` or `product-engineer`.
|
|
212
212
|
|
|
213
|
+
## Runbook-Coverage Finding (FR-49b)
|
|
214
|
+
|
|
215
|
+
S-003 created the runbooks and S-004 made their structure a `lint` gate.
|
|
216
|
+
Neither notices a runbook that was never written. That judgment —
|
|
217
|
+
"was this procedure worth writing down?" — is not deterministic, so it
|
|
218
|
+
lives here as a finding rather than in `core/checks`.
|
|
219
|
+
|
|
220
|
+
**Trigger.** Report the finding when both hold:
|
|
221
|
+
|
|
222
|
+
1. The pull request's task list contains **three or more** steps touching
|
|
223
|
+
configuration, environment, tooling, credentials, or data — setup,
|
|
224
|
+
configuration, or migration work — and
|
|
225
|
+
2. the PR adds or updates **no** runbook under `docs/runbooks/`.
|
|
226
|
+
|
|
227
|
+
The threshold is three, stated so the judgment is bounded rather than
|
|
228
|
+
open-ended. Two such steps is below it and is not a finding.
|
|
229
|
+
|
|
230
|
+
**Not a finding:**
|
|
231
|
+
|
|
232
|
+
- A PR with three or more such steps that **updates an existing runbook**.
|
|
233
|
+
Updating is delivering; a new file is not required.
|
|
234
|
+
- A docs-only PR. It is not performing the procedure.
|
|
235
|
+
- A PR whose steps are ordinary code changes, however many.
|
|
236
|
+
|
|
237
|
+
**The finding is advisory.** Like every other drift item it is
|
|
238
|
+
**non-blocking to PR readiness and to issue completion**, and it routes
|
|
239
|
+
to `product-engineer`'s `activity-drift-reconciliation` flow. Classify it
|
|
240
|
+
with the existing impact/intent vocabulary — this is a new trigger, not a
|
|
241
|
+
new category. Never hold a PR on it.
|
|
242
|
+
|
|
243
|
+
**Owners**, so the finding names someone rather than the air:
|
|
244
|
+
|
|
245
|
+
| Work kind | Owner |
|
|
246
|
+
| ----------------------------------- | ---------------- |
|
|
247
|
+
| Platform and infrastructure changes | `infra-engineer` |
|
|
248
|
+
| Setup and migration tasks | `developer` |
|
|
249
|
+
| Test-harness setup | `qa-engineer` |
|
|
250
|
+
| Tooling setup | `housekeeping` |
|
|
251
|
+
|
|
252
|
+
## Roadmap-Mismatch Finding
|
|
253
|
+
|
|
254
|
+
`docs/roadmap.md` is the one-page index of every PRD's phases or waves and their status. It goes stale silently unless something compares it with what actually merged, so that comparison lives here as a finding.
|
|
255
|
+
|
|
256
|
+
**Trigger** (PRD-level rollup audits, and story audits whose story completes a phase or wave). Report the finding when any of these hold:
|
|
257
|
+
|
|
258
|
+
1. The audited work completes a PRD phase or wave, and its roadmap row is not `Done` in the delivered tree.
|
|
259
|
+
2. A roadmap row is `Done`, but the audited scope shows that phase's stories unmerged or its acceptance criteria unmet.
|
|
260
|
+
3. The audited PRD defines a phase or wave with no roadmap row, or `docs/roadmap.md` is missing while `docs/requirements/` holds a PRD.
|
|
261
|
+
4. A row's `Issues/PRs` or `What's missing` contradicts the audited issues and PRs.
|
|
262
|
+
|
|
263
|
+
**Not a finding:** rows for PRDs outside the audited scope; a row left `In progress` while some of its stories are still open.
|
|
264
|
+
|
|
265
|
+
**The finding is advisory.** Like every other drift item it is **non-blocking to PR readiness and to issue completion**, and it routes to `product-engineer`'s `activity-drift-reconciliation` flow, which corrects the row. Classify it with the existing impact/intent vocabulary. Never hold a PR on it.
|
|
266
|
+
|
|
213
267
|
## Failure Triage Workflow (Randomized Tests)
|
|
214
268
|
|
|
215
269
|
When a randomized or fuzz test fails, follow this sequence:
|
|
@@ -262,6 +316,8 @@ The report **MUST** present sections in this order, so the verdict is visible fi
|
|
|
262
316
|
3. **Per-AC result table** — `AC-ID | Description | Codebase evidence | Workstream evidence | Test evidence | Result (Pass/Fail/Drift)`.
|
|
263
317
|
4. **Drift catalog** — for each drift item: description, impact class (Critical/Major/Minor), intent class (Intended/Unintended/Undetermined), evidence source(s), and an explicit note that drift is non-blocking to completion.
|
|
264
318
|
5. **Edge-case and randomized test outcomes** (when a prior test plan exists for this scope).
|
|
319
|
+
- **Documentation structure** — the `checkDocsStructure` result for the delivered tree. Failures are already a `lint` gate and so should be absent by the time this runs; staleness findings (`last_verified` over 90 days) are reported here and are non-blocking (D-21). A repository with no `docs/runbooks/` produces no findings and needs no note.
|
|
320
|
+
- **Vocabulary conformance** — the `checkExportedIdentifiers` result for the PR's added lines. Each hit names a new exported identifier, the text it matched, the forbidden synonym, and the term that forbids it. This is an **advisory** finding class: report every hit, and **never block** PR readiness on one (D-63). Extraction is a regex over `export` declarations rather than a parser (D-60), so an occasional false positive is expected — say so, rather than asking for a rename you do not believe in. Only forbidden synonyms are reported; an identifier that matches a canonical term is the name working as intended (D-64). A repository with no glossary, or one whose terms forbid nothing, produces no findings and needs no note.
|
|
265
321
|
6. **Recommendations** — suggested next step per drift item (`developer` fix, `product-engineer` spec clarification, or `no action needed`), without directly applying any change.
|
|
266
322
|
|
|
267
323
|
## Output Contract
|
|
@@ -54,13 +54,97 @@ block() {
|
|
|
54
54
|
exit 2
|
|
55
55
|
}
|
|
56
56
|
|
|
57
|
+
# Split the raw command into simple-command segments, one per output line,
|
|
58
|
+
# at `&&`, `||`, `;`, `|`, `&`, and newlines outside single or double quotes
|
|
59
|
+
# (backslash escapes honored). Every rule that reads a command's arguments
|
|
60
|
+
# reads them from its own segment, never from the rest of the string. Before
|
|
61
|
+
# this, `git push -u origin feat && gh pr create --base main` read `main` as
|
|
62
|
+
# a push destination, `--tags` anywhere in the string read as a tag push, and
|
|
63
|
+
# a greedy `.*git push` match checked only the LAST push in a chained
|
|
64
|
+
# command, so `git push origin main && git push origin feat` was allowed
|
|
65
|
+
# (issue #256). Portable awk only: macOS ships BSD awk, not gawk.
|
|
66
|
+
command_segments() {
|
|
67
|
+
printf '%s\n' "$cmd" | awk '
|
|
68
|
+
{ s = s (NR > 1 ? "\n" : "") $0 }
|
|
69
|
+
END {
|
|
70
|
+
out = ""; q = ""; n = length(s)
|
|
71
|
+
for (i = 1; i <= n; i++) {
|
|
72
|
+
c = substr(s, i, 1)
|
|
73
|
+
if (q != "") {
|
|
74
|
+
# Inside quotes a newline is part of the argument, never a
|
|
75
|
+
# separator: map it to a space so the segment stays whole.
|
|
76
|
+
if (c == "\n") { out = out " "; continue }
|
|
77
|
+
if (c == q) { q = ""; out = out c; continue }
|
|
78
|
+
if (c == "\\" && q == "\"" && i < n) {
|
|
79
|
+
d = substr(s, i + 1, 1); i++
|
|
80
|
+
if (d != "\n") out = out c d # backslash-newline is a continuation
|
|
81
|
+
continue
|
|
82
|
+
}
|
|
83
|
+
out = out c
|
|
84
|
+
continue
|
|
85
|
+
}
|
|
86
|
+
if (c == "\\" && i < n) {
|
|
87
|
+
d = substr(s, i + 1, 1); i++
|
|
88
|
+
if (d != "\n") out = out c d # backslash-newline is a continuation
|
|
89
|
+
continue
|
|
90
|
+
}
|
|
91
|
+
if (c == "\"" || c == "\047") { q = c; out = out c; continue }
|
|
92
|
+
if (c == ";" || c == "|" || c == "&" || c == "\n") { out = out "\n"; continue }
|
|
93
|
+
out = out c
|
|
94
|
+
}
|
|
95
|
+
print out
|
|
96
|
+
}'
|
|
97
|
+
}
|
|
98
|
+
|
|
99
|
+
# Segments matching the extended regex $1, whitespace-normalized, one per line.
|
|
100
|
+
segments_matching() {
|
|
101
|
+
command_segments | tr -s ' \t' ' ' | grep -E -- "$1"
|
|
102
|
+
}
|
|
103
|
+
|
|
104
|
+
# Argument tokens following EACH `git push` in segment $1, one per line.
|
|
105
|
+
# Quotes, backticks, parentheses, and separators are stripped from tokens so
|
|
106
|
+
# `$(git push origin main)` and `bash -c "git push origin main"` still yield
|
|
107
|
+
# `main`. Every occurrence in the segment is read, not just the last one.
|
|
108
|
+
push_tokens() {
|
|
109
|
+
printf '%s\n' "$1" | awk '{ n = split($0, parts, /git[ \t]+push/); for (i = 2; i <= n; i++) print parts[i] }' \
|
|
110
|
+
| tr -s ' \t' '\n\n' | tr -d "\"'\`();|&" | sed 's/[<>].*//' | grep -v '^$'
|
|
111
|
+
}
|
|
112
|
+
|
|
113
|
+
# A command word counts when it appears at a segment's start, after
|
|
114
|
+
# whitespace, after an opening quote, backtick, or parenthesis, or after a
|
|
115
|
+
# path (`/usr/bin/git`).
|
|
116
|
+
_cmd_prefix="(^|[[:space:](\`\"'/])"
|
|
117
|
+
_push_segment_re="${_cmd_prefix}git +push([[:space:]]|$)"
|
|
118
|
+
|
|
119
|
+
# Does any `git push` destination in the command equal branch $1? Reads each
|
|
120
|
+
# push segment's own tokens only; checks bare tokens and the right-hand side
|
|
121
|
+
# of `src:dst` refspecs, stripping a leading `+` and a `refs/heads/` prefix.
|
|
122
|
+
push_targets_ref() {
|
|
123
|
+
local target="$1" seg tok dst
|
|
124
|
+
while IFS= read -r seg; do
|
|
125
|
+
while IFS= read -r tok; do
|
|
126
|
+
case "$tok" in
|
|
127
|
+
-*) continue ;;
|
|
128
|
+
esac
|
|
129
|
+
tok="${tok#+}"
|
|
130
|
+
dst="${tok##*:}"
|
|
131
|
+
tok="${tok#refs/heads/}"
|
|
132
|
+
dst="${dst#refs/heads/}"
|
|
133
|
+
if [ "$tok" = "$target" ] || [ "$dst" = "$target" ]; then
|
|
134
|
+
return 0
|
|
135
|
+
fi
|
|
136
|
+
done < <(push_tokens "$seg")
|
|
137
|
+
done < <(segments_matching "$_push_segment_re")
|
|
138
|
+
return 1
|
|
139
|
+
}
|
|
140
|
+
|
|
57
141
|
# --- Rule 1: never merge/push into main ---------------------------------------
|
|
58
|
-
# Block
|
|
59
|
-
#
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
142
|
+
# Block a push whose destination is main, and any merge/PR-merge that targets
|
|
143
|
+
# main. Branch-creation and normal feature pushes are unaffected, including a
|
|
144
|
+
# feature push chained with `gh pr create --base main` (issue #256).
|
|
145
|
+
if push_targets_ref main; then
|
|
146
|
+
block "pushing to 'main' is not allowed. Open a PR; only the user may merge into main."
|
|
147
|
+
fi
|
|
64
148
|
|
|
65
149
|
# `git merge` while the checked-out branch is main (i.e. merging INTO main).
|
|
66
150
|
if printf '%s' "$norm" | grep -Eq '(^|[;&|[:space:]])git +merge([[:space:]]|$)'; then
|
|
@@ -71,17 +155,19 @@ if printf '%s' "$norm" | grep -Eq '(^|[;&|[:space:]])git +merge([[:space:]]|$)';
|
|
|
71
155
|
fi
|
|
72
156
|
|
|
73
157
|
# `gh pr merge` targeting main (either via --base main or merging a PR onto main).
|
|
74
|
-
|
|
75
|
-
|
|
158
|
+
# Checked per segment, so a later `gh pr create --base main` in the same
|
|
159
|
+
# command is not read as this merge's base (issue #256).
|
|
160
|
+
while IFS= read -r _seg; do
|
|
161
|
+
if printf '%s' "$_seg" | grep -Eq -- "(--base|-B)[ =][\"']?main([^[:alnum:]_./-]|$)"; then
|
|
76
162
|
block "merging a PR into 'main' is not allowed. Only the user may merge into main."
|
|
77
163
|
fi
|
|
78
164
|
# No explicit base given: gh defaults to the PR's base. Warn-block to be safe
|
|
79
165
|
# for the common case where PRs target main. Story PRs targeting integration
|
|
80
166
|
# branches should pass --base <integration-branch> explicitly.
|
|
81
|
-
if ! printf '%s' "$
|
|
167
|
+
if ! printf '%s' "$_seg" | grep -Eq -- '--base[ =]|-B[ =]'; then
|
|
82
168
|
block "refusing 'gh pr merge' without an explicit --base. PRs to main require user approval; for integration branches pass --base <integration-branch>."
|
|
83
169
|
fi
|
|
84
|
-
|
|
170
|
+
done < <(segments_matching 'gh +pr +merge')
|
|
85
171
|
|
|
86
172
|
# --- Rule 2: Conventional Commits for git commit ------------------------------
|
|
87
173
|
# Inspect inline -m / --message messages. Commits via editor or -F file are not
|
|
@@ -80,13 +80,7 @@ The artifact **MUST** contain exactly these ten sections, in this order:
|
|
|
80
80
|
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
81
|
3. Identify the target scope: files, directories, modules, or packages likely relevant.
|
|
82
82
|
|
|
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
|
|
83
|
+
### Phase 2 — Slice Execution
|
|
90
84
|
|
|
91
85
|
For each of the eight slices (S1-S8):
|
|
92
86
|
|
|
@@ -95,7 +89,7 @@ For each of the eight slices (S1-S8):
|
|
|
95
89
|
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
90
|
4. Rank findings by relevance to the research question, not alphabetically.
|
|
97
91
|
|
|
98
|
-
### Phase
|
|
92
|
+
### Phase 3 — Synthesis
|
|
99
93
|
|
|
100
94
|
1. Write the **Answer first** section: directly answer the research question in <= 10 lines using the evidence gathered.
|
|
101
95
|
2. Compile the **Relevance-ranked file map** from the top findings across all slices (max 30 files).
|
|
@@ -105,13 +99,13 @@ For each of the eight slices (S1-S8):
|
|
|
105
99
|
6. Populate **Not investigated** with areas deliberately skipped (out of scope, budget exhausted, tooling unavailable).
|
|
106
100
|
7. Assign a **Confidence** level based on coverage completeness, source quality, and known gaps.
|
|
107
101
|
|
|
108
|
-
### Phase
|
|
102
|
+
### Phase 4 — Budget Enforcement
|
|
109
103
|
|
|
110
104
|
1. Count report lines. If > 250, remove the lowest-relevance findings until compliant and record omissions under "Not Investigated".
|
|
111
105
|
2. Count cited files. If > 30, collapse the lowest-relevance entries and record omissions.
|
|
112
106
|
3. Final check: all ten sections present and in order; all eight slices addressed; both caps satisfied.
|
|
113
107
|
|
|
114
|
-
### Phase
|
|
108
|
+
### Phase 5 — Provenance and Output
|
|
115
109
|
|
|
116
110
|
1. Record in Provenance:
|
|
117
111
|
- Repository name
|
|
@@ -120,7 +114,6 @@ For each of the eight slices (S1-S8):
|
|
|
120
114
|
- Invoking agent (e.g., `product-engineer`, `developer`, `planner`)
|
|
121
115
|
- Research question (verbatim)
|
|
122
116
|
- Date (ISO 8601)
|
|
123
|
-
- Multi-repo source: `dt context` or `direct scanning (fallback)`
|
|
124
117
|
2. Write the artifact to the contract path.
|
|
125
118
|
3. Optionally post a one-line summary as a GitHub issue comment.
|
|
126
119
|
|
|
@@ -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).
|