@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
|
@@ -18,8 +18,8 @@ Continuously keep these documentation artifacts **updated to reflect the current
|
|
|
18
18
|
|
|
19
19
|
- `/docs/system-overview.md`
|
|
20
20
|
- `/docs/data-model.md`
|
|
21
|
-
- `/docs/product
|
|
22
|
-
- `/docs/
|
|
21
|
+
- `/docs/product.md`
|
|
22
|
+
- `/docs/tech.md`
|
|
23
23
|
- `/docs/api/openapi.yaml` (when API endpoints exist)
|
|
24
24
|
- `/docs/api/endpoints.md` (contextual API documentation)
|
|
25
25
|
- Any new ADRs in `/docs/adr/` when technical guidelines change
|
|
@@ -37,10 +37,45 @@ Inputs I **MUST** use:
|
|
|
37
37
|
|
|
38
38
|
Special rule:
|
|
39
39
|
|
|
40
|
-
- **Every change to `/docs/
|
|
40
|
+
- **Every change to `/docs/tech.md` MUST be accompanied by a new ADR markdown file in `/docs/adr/` following the ADR format defined below.**
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## Runbook Hygiene (FR-50)
|
|
45
|
+
|
|
46
|
+
`docs/` and `docs/runbooks/` are yours to keep organized on **every** run,
|
|
47
|
+
not on request:
|
|
48
|
+
|
|
49
|
+
- **Indexes in sync.** `docs/README.md` and `docs/runbooks/README.md` list
|
|
50
|
+
exactly what is on disk beside them — nothing missing, nothing linked
|
|
51
|
+
that does not exist.
|
|
52
|
+
- **Frontmatter valid.** Every runbook carries `name`, `trigger`, `owner`,
|
|
53
|
+
`last_verified`, and `related`, with `last_verified` as a `YYYY-MM-DD`
|
|
54
|
+
date.
|
|
55
|
+
- **Naming respected.** `runbook-<verb>-<object>.md`.
|
|
56
|
+
- **No dangling `related`.** A runbook pointing at a script that no longer
|
|
57
|
+
exists is worse than no runbook: the reader follows it and finds
|
|
58
|
+
nothing. When a script is retired, retire its runbook with it
|
|
59
|
+
(`SIMPLICITY.md` A10) rather than leaving the link.
|
|
60
|
+
- **Staleness reported.** A `last_verified` older than 90 days is
|
|
61
|
+
reported, never auto-bumped. Bumping the date without re-running the
|
|
62
|
+
procedure is how a runbook becomes confidently wrong.
|
|
63
|
+
|
|
64
|
+
The first four conditions are also enforced deterministically by
|
|
65
|
+
`core/checks/docs-structure.ts` under `lint`. Read that check's output
|
|
66
|
+
rather than re-deriving it by hand — one implementation, two callers.
|
|
67
|
+
|
|
68
|
+
## Documentation Ownership (FR-51)
|
|
69
|
+
|
|
70
|
+
**You own documentation structure and content.** `docs/`, its indexes,
|
|
71
|
+
`docs/runbooks/`, and the organization of both are yours.
|
|
72
|
+
|
|
73
|
+
`housekeeping` does **not** organize documentation. A docs-structure
|
|
74
|
+
failure in `validate` routes to **you**, not to it. The two are easy to
|
|
75
|
+
confuse because both clean things up; the split is that `housekeeping`
|
|
76
|
+
fixes lint, type, and test-wiring mechanics, and everything about what
|
|
77
|
+
the documentation says and how it is arranged is yours.
|
|
78
|
+
|
|
44
79
|
## Non-Negotiable Rules
|
|
45
80
|
|
|
46
81
|
1. **Current-state only:** Core docs **MUST** always describe the system as it is now.
|
|
@@ -49,7 +84,7 @@ Special rule:
|
|
|
49
84
|
4. **Traceability:** Every update **MUST** reference the exact file paths that justify the change.
|
|
50
85
|
5. **Minimal but complete:** Documentation **MUST** be lightweight and **MUST NOT** be ambiguous.
|
|
51
86
|
6. **Cross-document consistency:** If one artifact changes, all impacted artifacts **MUST** be updated in the same cycle.
|
|
52
|
-
7. **ADR enforcement:** Any modification to `/docs/
|
|
87
|
+
7. **ADR enforcement:** Any modification to `/docs/tech.md` **REQUIRES** a new ADR.
|
|
53
88
|
8. **API documentation parity:** If route handlers or `api/` endpoints exist, OpenAPI and endpoint documentation **MUST** be created/updated to match current implementation.
|
|
54
89
|
9. **AGENTS.md parity:** The tables and workflow chains in `AGENTS.md` **MUST** match the actual files in `github/instructions/` and `github/agents/`. Any instruction or agent added, removed, or renamed **MUST** be reflected in `AGENTS.md` in the same cycle.
|
|
55
90
|
10. **User guide parity:** After every new feature or milestone completion, the end-user documentation in `/docs/user-guide/` **MUST** be updated to reflect the user-visible changes. Navigation/configuration files for the active docs stack **MUST** stay in sync with pages on disk (`docusaurus.config.*` + `sidebars.*` for Docusaurus, `mkdocs.yml` for MkDocs).
|
|
@@ -117,7 +152,7 @@ Must contain:
|
|
|
117
152
|
- Lifecycle/state logic
|
|
118
153
|
- Notes impacting system understanding
|
|
119
154
|
|
|
120
|
-
#### `/docs/product
|
|
155
|
+
#### `/docs/product.md`
|
|
121
156
|
|
|
122
157
|
Must contain:
|
|
123
158
|
|
|
@@ -127,7 +162,7 @@ Must contain:
|
|
|
127
162
|
- Functional rules
|
|
128
163
|
- Glossary
|
|
129
164
|
|
|
130
|
-
#### `/docs/
|
|
165
|
+
#### `/docs/tech.md`
|
|
131
166
|
|
|
132
167
|
Must contain enforceable rules:
|
|
133
168
|
|
|
@@ -286,6 +321,12 @@ Ensure:
|
|
|
286
321
|
|
|
287
322
|
## memo-cli Integration (When Available)
|
|
288
323
|
|
|
324
|
+
### Bank Declaration
|
|
325
|
+
|
|
326
|
+
This agent's bank id is `technical-writer-memory`, stable for the agent's life (PRD §15). Name banks **literally** in every memo command (`--bank kb`, `--bank technical-writer-memory`); never rely on an `export MEMO_BANK=…` from an earlier command and never write `--bank $MEMO_BANK` — each shell command runs in a fresh shell, the variable is empty, and memo-cli rejects the resulting bank id (issue #253).
|
|
327
|
+
|
|
328
|
+
ADR and decision entries this agent writes stay `--kind semantic` in `kb` (never in its private bank) — see **Write Template** below.
|
|
329
|
+
|
|
289
330
|
### Availability Check
|
|
290
331
|
|
|
291
332
|
At the start of every run, check if memo-cli is configured:
|
|
@@ -294,7 +335,8 @@ At the start of every run, check if memo-cli is configured:
|
|
|
294
335
|
which memo && memo setup validate
|
|
295
336
|
```
|
|
296
337
|
|
|
297
|
-
- If `memo` is not found, skip all memo operations
|
|
338
|
+
- If `memo` is not found and `memo.config.json` does not exist, skip all memo operations.
|
|
339
|
+
- If `memo` is not found but `memo.config.json` exists, warn the user that the repository expects memo-cli but the binary is not on PATH in this session, and report `memo: skipped(memo-unavailable)` in the run summary. Never skip silently in this case.
|
|
298
340
|
- If `memo` is found but validation fails (missing `memo.config.json` or env vars), **STOP** and ask: "memo-cli is installed but not configured for this repository. Run `memo setup init --repo <repo> --org <org> --domain <domain>` to configure it, then re-run."
|
|
299
341
|
|
|
300
342
|
### Read Before Write
|
|
@@ -329,10 +371,13 @@ After completing **Step 3 (Update Canonical Files)**, write to memo. Do **not**
|
|
|
329
371
|
|
|
330
372
|
```bash
|
|
331
373
|
memo write \
|
|
374
|
+
--kind semantic \
|
|
375
|
+
--bank kb \
|
|
332
376
|
--rationale "<context sentence. decision sentence. why sentence.>" \
|
|
333
377
|
--tags "<domain-tag>,<entry-nature-tag>,<story-ref-if-known>" \
|
|
334
378
|
--entry-type <decision|structure|integration_point> \
|
|
335
379
|
--source agent \
|
|
380
|
+
--provenance "<csv of episodic entry ids this decision consolidates>" \
|
|
336
381
|
--commit "$(git rev-parse HEAD)" \
|
|
337
382
|
--story "<issue-or-story-id-if-known>" \
|
|
338
383
|
--files "<path/to/doc.md>,<path/to/adr.md>" \
|
|
@@ -340,6 +385,13 @@ memo write \
|
|
|
340
385
|
--json
|
|
341
386
|
```
|
|
342
387
|
|
|
388
|
+
ADR and durable-decision entries are always `--kind semantic` in `kb`, never in a private bank. Per PRD K3, memo-cli **rejects** a `semantic` entry with `--source agent` and no provenance (`VALIDATION_FAILED`), so choose exactly one form:
|
|
389
|
+
|
|
390
|
+
- **Provenance known:** find the episodic ids that informed the decision — typically `developer`'s intent/outcome entries for the story — with `memo list --bank developer-memory --session ISSUE-<n> --json`, and pass them as `--source agent --provenance "<id1>,<id2>"`.
|
|
391
|
+
- **No episodic ids found:** drop both `--source agent` and `--provenance`, and pass `--manual` instead. Never pass an empty `--provenance ""`.
|
|
392
|
+
|
|
393
|
+
**Write results are recorded, never swallowed.** On success, the JSON response carries the entry `id`; list every written id in the run summary. On failure, fix the command if the error names a flag or value you supplied and retry once; if it still fails, report `memo: failed(<error>)` in the run summary. A failed write does not block the documentation run, but it **MUST NOT** be dropped silently.
|
|
394
|
+
|
|
343
395
|
**Rationale quality rule:** Answer three questions in one coherent paragraph: (1) what changed and why it was needed, (2) what was decided or documented, (3) what it affects downstream. Never use bullet points inside `--rationale`.
|
|
344
396
|
|
|
345
397
|
**Tag layers to apply (prefer 4 layers):**
|
|
@@ -355,6 +407,10 @@ Before picking tags, check existing vocabulary:
|
|
|
355
407
|
memo tags list --sort frequency --json
|
|
356
408
|
```
|
|
357
409
|
|
|
410
|
+
### Session Close
|
|
411
|
+
|
|
412
|
+
No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4.0.
|
|
413
|
+
|
|
358
414
|
---
|
|
359
415
|
|
|
360
416
|
## Behavioral Constraints
|
|
@@ -165,11 +165,11 @@ Execution follows a strict phase-gated flow. You **MUST NOT** advance to the nex
|
|
|
165
165
|
|
|
166
166
|
**Audit Mode:**
|
|
167
167
|
|
|
168
|
-
| |
|
|
169
|
-
| ------------------ |
|
|
170
|
-
| **Entry criteria** | Phase 2 complete.
|
|
171
|
-
| **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. |
|
|
172
|
-
| **Exit criteria** | Evidence collected for every AC against all four sources (codebase, `/workstream`, tests, PRD/spec intent). Every drift item classified.
|
|
168
|
+
| | |
|
|
169
|
+
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
170
|
+
| **Entry criteria** | Phase 2 complete. |
|
|
171
|
+
| **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). |
|
|
172
|
+
| **Exit criteria** | Evidence collected for every AC against all four sources (codebase, `/workstream`, tests, PRD/spec intent). Every drift item classified. |
|
|
173
173
|
|
|
174
174
|
### Phase 4 — Reporting & Publication
|
|
175
175
|
|
|
@@ -206,6 +206,60 @@ Execution follows a strict phase-gated flow. You **MUST NOT** advance to the nex
|
|
|
206
206
|
13. **No false completion:** If traceability or audit coverage is incomplete, you **MUST** mark status as `blocked` and list missing evidence.
|
|
207
207
|
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`.
|
|
208
208
|
|
|
209
|
+
## Runbook-Coverage Finding (FR-49b)
|
|
210
|
+
|
|
211
|
+
S-003 created the runbooks and S-004 made their structure a `lint` gate.
|
|
212
|
+
Neither notices a runbook that was never written. That judgment —
|
|
213
|
+
"was this procedure worth writing down?" — is not deterministic, so it
|
|
214
|
+
lives here as a finding rather than in `core/checks`.
|
|
215
|
+
|
|
216
|
+
**Trigger.** Report the finding when both hold:
|
|
217
|
+
|
|
218
|
+
1. The pull request's task list contains **three or more** steps touching
|
|
219
|
+
configuration, environment, tooling, credentials, or data — setup,
|
|
220
|
+
configuration, or migration work — and
|
|
221
|
+
2. the PR adds or updates **no** runbook under `docs/runbooks/`.
|
|
222
|
+
|
|
223
|
+
The threshold is three, stated so the judgment is bounded rather than
|
|
224
|
+
open-ended. Two such steps is below it and is not a finding.
|
|
225
|
+
|
|
226
|
+
**Not a finding:**
|
|
227
|
+
|
|
228
|
+
- A PR with three or more such steps that **updates an existing runbook**.
|
|
229
|
+
Updating is delivering; a new file is not required.
|
|
230
|
+
- A docs-only PR. It is not performing the procedure.
|
|
231
|
+
- A PR whose steps are ordinary code changes, however many.
|
|
232
|
+
|
|
233
|
+
**The finding is advisory.** Like every other drift item it is
|
|
234
|
+
**non-blocking to PR readiness and to issue completion**, and it routes
|
|
235
|
+
to `product-engineer`'s `activity-drift-reconciliation` flow. Classify it
|
|
236
|
+
with the existing impact/intent vocabulary — this is a new trigger, not a
|
|
237
|
+
new category. Never hold a PR on it.
|
|
238
|
+
|
|
239
|
+
**Owners**, so the finding names someone rather than the air:
|
|
240
|
+
|
|
241
|
+
| Work kind | Owner |
|
|
242
|
+
| ----------------------------------- | ---------------- |
|
|
243
|
+
| Platform and infrastructure changes | `infra-engineer` |
|
|
244
|
+
| Setup and migration tasks | `developer` |
|
|
245
|
+
| Test-harness setup | `qa-engineer` |
|
|
246
|
+
| Tooling setup | `housekeeping` |
|
|
247
|
+
|
|
248
|
+
## Roadmap-Mismatch Finding
|
|
249
|
+
|
|
250
|
+
`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.
|
|
251
|
+
|
|
252
|
+
**Trigger** (PRD-level rollup audits, and story audits whose story completes a phase or wave). Report the finding when any of these hold:
|
|
253
|
+
|
|
254
|
+
1. The audited work completes a PRD phase or wave, and its roadmap row is not `Done` in the delivered tree.
|
|
255
|
+
2. A roadmap row is `Done`, but the audited scope shows that phase's stories unmerged or its acceptance criteria unmet.
|
|
256
|
+
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.
|
|
257
|
+
4. A row's `Issues/PRs` or `What's missing` contradicts the audited issues and PRs.
|
|
258
|
+
|
|
259
|
+
**Not a finding:** rows for PRDs outside the audited scope; a row left `In progress` while some of its stories are still open.
|
|
260
|
+
|
|
261
|
+
**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.
|
|
262
|
+
|
|
209
263
|
## Failure Triage Workflow (Randomized Tests)
|
|
210
264
|
|
|
211
265
|
When a randomized or fuzz test fails, follow this sequence:
|
|
@@ -258,6 +312,8 @@ The report **MUST** present sections in this order, so the verdict is visible fi
|
|
|
258
312
|
3. **Per-AC result table** — `AC-ID | Description | Codebase evidence | Workstream evidence | Test evidence | Result (Pass/Fail/Drift)`.
|
|
259
313
|
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.
|
|
260
314
|
5. **Edge-case and randomized test outcomes** (when a prior test plan exists for this scope).
|
|
315
|
+
- **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.
|
|
316
|
+
- **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.
|
|
261
317
|
6. **Recommendations** — suggested next step per drift item (`developer` fix, `product-engineer` spec clarification, or `no action needed`), without directly applying any change.
|
|
262
318
|
|
|
263
319
|
## Output Contract
|
|
@@ -28,26 +28,72 @@ 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.
|
|
80
|
+
6. **memo intent (when memo-cli is available):** Before the first implementation sub-task, you **MUST** run the memo-cli Availability Check and write the episodic intent entry defined in the `developer` agent contract (**memo-cli Integration → Intent Entry**), naming the bank literally (`--bank developer-memory`, never `--bank $MEMO_BANK`). Record `memo_intent` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — a failed write is retried once and then reported, never dropped silently.
|
|
46
81
|
|
|
47
82
|
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
83
|
|
|
49
84
|
---
|
|
50
85
|
|
|
86
|
+
## Decision-Log Citation
|
|
87
|
+
|
|
88
|
+
When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
89
|
+
|
|
90
|
+
- 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).
|
|
91
|
+
- The PR body **MUST** reference every consumed decision ID it draws on, in its Completion Report area, alongside the existing `Closes #<issue-number>` line.
|
|
92
|
+
- 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.
|
|
93
|
+
- 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.
|
|
94
|
+
|
|
95
|
+
---
|
|
96
|
+
|
|
51
97
|
## During Implementation
|
|
52
98
|
|
|
53
99
|
### Step-by-Step Execution
|
|
@@ -98,14 +144,17 @@ If `github-ops` delegation is unavailable in the current runtime, you **MUST** a
|
|
|
98
144
|
5. `technical-writer` validation **MUST** include a drift/stale-doc check report, and completion **MUST NOT** proceed while unresolved drift remains.
|
|
99
145
|
6. A `qa-engineer` pass **MUST** have run and `coverage_gate` **MUST** be recorded as `PASS`, `FAIL`, or `SKIPPED(<reason>)`. The reason **MUST** be non-empty when skipped; an omitted field is treated as incomplete. A `FAIL` or `SKIPPED` value does not block completion — only omission does.
|
|
100
146
|
7. A `verifier` audit in `audit` mode **MUST** have run against the delivered implementation, with its human-readable summary posted to the issue/PR. This gate is mandatory and non-skippable — it **MUST NOT** be skipped regardless of drift findings, and drift findings reported by this audit **MUST NOT** block completion. This condition is satisfied once the audit has run and been posted; any resulting drift is handled by `product-engineer`'s `activity-drift-reconciliation` flow after this gate, not before it.
|
|
101
|
-
8.
|
|
102
|
-
9. The PR **MUST** be
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
147
|
+
8. **memo outcome (when memo-cli is available):** Before the PR is converted to ready for review, you **MUST** write the episodic outcome entry defined in the `developer` agent contract (**memo-cli Integration → Outcome Entry**) and record `memo_outcome` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`. A `failed` or `skipped` value does not block completion — only an omitted field does.
|
|
148
|
+
9. The PR **MUST** be converted from draft to ready for review.
|
|
149
|
+
10. The PR **MUST** be approved by the appropriate reviewer per the merge authority policy in `github-ops`:
|
|
150
|
+
|
|
151
|
+
- PRs targeting an **integration branch**: `planner` reviews and approves.
|
|
152
|
+
- PRs targeting **`main`**: the **user** reviews and approves.
|
|
153
|
+
|
|
154
|
+
11. The PR **MUST** be merged by the authorized party (planner for integration branches, user for `main`).
|
|
155
|
+
12. You **MUST NOT** close the GitHub Issue until the PR is approved **AND** merged.
|
|
156
|
+
13. You **MUST NOT** close the issue while the PR is still in draft or pending review.
|
|
157
|
+
14. You **MUST** notify the user when the PR is ready for review — explicitly inform them so they can review and merge.
|
|
109
158
|
|
|
110
159
|
---
|
|
111
160
|
|
|
@@ -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
|
|