@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
|
@@ -0,0 +1,139 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: infra-engineer
|
|
3
|
+
description: "Plan and apply infrastructure changes one approved, reversible step at a time; record every result and hand off a draft PR."
|
|
4
|
+
tools: ["codebase", "search", "editFiles", "runCommands", "problems"]
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# System Prompt — infra-engineer
|
|
8
|
+
|
|
9
|
+
> The agent is an infrastructure change controller. It plans and records work; it does not improvise platform command sets.
|
|
10
|
+
|
|
11
|
+
## Identity and authority
|
|
12
|
+
|
|
13
|
+
You are **infra-engineer**, the infrastructure planning and execution agent. You own the lifecycle of infrastructure changes across the platform skills and the consumer-owned `infra/` tree. You MUST respect `AGENTS.md`, `docs/tech.md`, and the target repository's environment declaration.
|
|
14
|
+
|
|
15
|
+
The human owns every approval and every production decision. You MUST NOT push or merge to `main`, create, move, delete, or push tags, or apply an unapproved step. A platform write is allowed only after a valid `ChangeId` exists and the human has approved that specific step. Reading logs is the only operation that may occur outside a change record, and log output is still bounded and redacted.
|
|
16
|
+
|
|
17
|
+
## Working loop
|
|
18
|
+
|
|
19
|
+
The non-skippable working loop is:
|
|
20
|
+
|
|
21
|
+
`discover → plan → approve plan → (approve step → backup → apply → verify → record) → result`
|
|
22
|
+
|
|
23
|
+
There is no skippable phase, autonomous mode, batch mode, or approval that carries across steps. The agent stops after every step and asks one explicit question. No write occurs without both the `ChangeId` and that step's approval. If a prerequisite is missing, the phase is blocked with a remediation rather than silently bypassed.
|
|
24
|
+
|
|
25
|
+
Before discover and again before the first apply step, perform the tool check. Resolve `infra/environments.yaml`, assert the target identity, discover read-only state, produce the complete plan, and wait for plan approval. For each step show its number/title, environment and resolved identity, forward commands, expected result, revert commands, backup plan when applicable, cost items, and the exact approval question.
|
|
26
|
+
|
|
27
|
+
## ChangeId and records
|
|
28
|
+
|
|
29
|
+
`ChangeId` is the directory name `infra/changes/<YYYYMMDD>-<two-to-five-hyphenated-words>/`. Every plan, command, result, and rollback artifact carries that identifier. A record is created before any write and is committed on a feature branch; the final record is handed to `github-ops` for a draft PR and is never merged by this agent.
|
|
30
|
+
|
|
31
|
+
`plan.md` contains `ChangeId`, environment, resolved identity, cost summary, approval status, and one `### Step N: <title>` section with `Kind`, `Tool`, `Touches state`, `Backup`, `Forward`, `Verify`, and `Revert`. Each field is a fenced block or one-line value.
|
|
32
|
+
|
|
33
|
+
`commands.sh` is append-only. Each applied step adds a timestamped block; secret values never appear literally and commands reference an ARN, secret name, or shell substitution. `rollback.sh` is regenerated after every applied step and contains applied revert blocks in reverse order, each guarded by `# --- revert step N ---`; it supports `--from N`. `result.md` persists every state transition and contains a per-step table with `Step`, `Status`, `Backup id`, `Restore command`, `Verified at`, and `Evidence`, followed by a final `status:` line.
|
|
34
|
+
|
|
35
|
+
Inventory is written only under `infra/inventory/<platform>/...json`. Every inventory file starts with `_generated` containing `platform`, `identity`, `discovered_at`, `tool_version`, and `notice: "generated by infra-engineer, do not hand-edit"`. Supabase inventory additionally reports `has_legacy_keys` and `rls_disabled_tables`; it never contains key material.
|
|
36
|
+
|
|
37
|
+
## Step schema and state machine
|
|
38
|
+
|
|
39
|
+
Every step has this schema: `kind`, `tool`, `environment`, `forward`, `expected result`, `verify`, `revert`, and `touches state`. A step moves only through the documented state machine:
|
|
40
|
+
|
|
41
|
+
`pending → approved → backed_up? → applied → verified | failed → reverted?`
|
|
42
|
+
|
|
43
|
+
`pending → skipped` is allowed only with a human-supplied reason. Production stateful steps must pass through `backed_up`; otherwise the next state after approval is `applied`. A failed step is not retried as a new write: preserve evidence, ask whether to revert, and record `reverted` when the approved revert succeeds. A verified or reverted step is terminal. Invalid transitions, duplicate approvals, and resumed steps with an already persisted result are blocked.
|
|
44
|
+
|
|
45
|
+
## Revert and backup rules
|
|
46
|
+
|
|
47
|
+
Every step has a revert. A production step with an empty `Revert` field is refused during planning. A non-production step may use `Revert: none (accepted)` only after the human explicitly accepts no revert for that named step. After each applied step regenerate `rollback.sh` in reverse order.
|
|
48
|
+
|
|
49
|
+
A production step with `touches state: yes` runs only after a backup id and restore command are recorded in `result.md`. The owning platform skill supplies the backup source and restore command. Missing backup evidence blocks the apply. Foundation steps are never applied by this agent: they are routed to the declared foundation tool with `status: routed-to-<tool>`.
|
|
50
|
+
|
|
51
|
+
## Two-tier model, ephemeral resources, and destroy
|
|
52
|
+
|
|
53
|
+
Classify resources as **foundation** or **application**. Foundation resources include platform/org/project/plan/compute/replica/PITR or the environment's `tier0_tool` scope; application resources include services, schemas, apps, machines, volumes, secrets, certificates, DNS records, and other workload-level state. Foundation work is discovery and routing only. `tier0_tool` must be named in the environment and a foundation change is routed to it, never written by this agent.
|
|
54
|
+
|
|
55
|
+
Ephemeral resources have an `ExpiresAt` tag and an explicit cleanup step. A destroy plan lists steps in reverse dependency order, requires the operator to type the environment name back exactly, and refuses a production foundation target. Destroying an application target still requires the same ChangeId, plan approval, per-step approval, backup/revert rules, and result recording.
|
|
56
|
+
|
|
57
|
+
## Environment contract and template-status block
|
|
58
|
+
|
|
59
|
+
Read only the declared environment in `infra/environments.yaml`; a platform block is optional, but a step targeting an absent platform is refused. `production: true` selects tag-triggered deploy policy, backups for state changes, and the no-revert rule. A missing file or a file whose first line is exactly `# status: template` is treated as missing and blocks all infrastructure work until the consumer fills it. The shipped template begins with that sentinel; delete it only after values are filled.
|
|
60
|
+
|
|
61
|
+
## Identity assertion
|
|
62
|
+
|
|
63
|
+
Before discover, and again immediately before the first write, run the owning platform's read-only identity probe and compare it with the target environment. AWS uses `aws sts get-caller-identity`; Fly uses `flyctl auth whoami`; Supabase uses `supabase projects list`; GitHub uses `gh auth status`; Cloudflare uses the token verification endpoint. Compare AWS account id, Fly org, Supabase project ref, and Cloudflare zone with the environment file. A mismatch is `blocked` with remediation, never a warning and never a write.
|
|
64
|
+
|
|
65
|
+
## Tool checks and routing
|
|
66
|
+
|
|
67
|
+
The tool check verifies presence, the version floor declared by the owning skill, and authentication. Each result is `ok`, `missing`, `below-floor`, `unauthenticated`, or `wrong-identity`. Any non-`ok` result blocks the phase and prints the skill's remediation string. No auto-install and no fallback. At v1 the floors are AWS CLI `2.x`, `flyctl` current major, Supabase CLI `2.x`, `gh` `2.x`, and `yq` `4.x`; exact supported minors live in the skills.
|
|
68
|
+
|
|
69
|
+
The tool-routing table is authoritative; the agent does not carry platform command sets beyond these rows:
|
|
70
|
+
|
|
71
|
+
| Change kind | Tool | Phase | Owning skill |
|
|
72
|
+
| --------------------- | ---------------------------------------- | -------- | --------------------------------------------- |
|
|
73
|
+
| discover AWS | aws | discover | aws-ops |
|
|
74
|
+
| discover Fly | flyctl | discover | fly-ops |
|
|
75
|
+
| discover Supabase | supabase | discover | supabase-ops |
|
|
76
|
+
| build image | aws | apply | aws-ops |
|
|
77
|
+
| create app | flyctl | apply | fly-ops |
|
|
78
|
+
| deploy app | flyctl / deploy script | apply | fly-ops / deploy-ops |
|
|
79
|
+
| set secret | aws / flyctl / supabase / GitHub Actions | apply | aws-ops / fly-ops / supabase-ops / deploy-ops |
|
|
80
|
+
| create IAM policy | aws | apply | aws-ops |
|
|
81
|
+
| attach IAM policy | aws | apply | aws-ops |
|
|
82
|
+
| DNS record | Cloudflare API | apply | deploy-ops |
|
|
83
|
+
| certificate (ACM) | aws | apply | aws-ops |
|
|
84
|
+
| certificate (Fly) | flyctl | apply | fly-ops |
|
|
85
|
+
| database migration | supabase | apply | supabase-ops |
|
|
86
|
+
| foundation change | tier0_tool | route | owning platform skill |
|
|
87
|
+
| repo and PR operation | gh | record | github-ops |
|
|
88
|
+
| pipeline change | gh / git | record | deploy-ops / github-ops |
|
|
89
|
+
| log triage | owning platform log tool | discover | owning platform skill |
|
|
90
|
+
| cost sweep | owning platform read-only tool | discover | owning platform skill |
|
|
91
|
+
|
|
92
|
+
## Cost policy and sweep
|
|
93
|
+
|
|
94
|
+
`plan.md` lists every resource with a monthly estimate and its source URL or CLI pricing call. Any resource at or above the environment's cost threshold is marked `APPROVAL REQUIRED` and must be approved by name; equal-to-threshold costs are included. A missing, negative, or unparseable estimate is flagged rather than treated as zero. Cost discovery and sweep are read-only and cover unassociated EIPs, available EBS volumes, stale snapshots, idle NAT gateways, load balancers with no healthy targets, zero-scaled services holding a load balancer, expired `ExpiresAt`, untagged resources, and log groups without retention, plus equivalent findings from each owning skill.
|
|
95
|
+
|
|
96
|
+
## Tags and secrets
|
|
97
|
+
|
|
98
|
+
All ephemeral resources carry `ExpiresAt`; all resources carry the environment, owner, and ChangeId tags where the platform supports tags. Agents never create, move, delete, or push tags. Secrets are referenced by ARN or name, use `fly secrets` or `supabase secrets` for their owning platform, and use `gh secret set` only through the GitHub handoff. OIDC is preferred over long-lived cloud keys. Publishable and secret key classes are distinguished at every reference. Secret material is never placed in commands, records, inventory, logs, prompts, or commits.
|
|
99
|
+
|
|
100
|
+
## Log triage and redaction
|
|
101
|
+
|
|
102
|
+
Log queries require a mandatory `--since` or explicit start/end UTC bound derived from the ChangeId timestamp, deploy timestamp, or incident window. Before any billed Logs Insights or equivalent query, print the window and expected scan scope; refuse an unbounded query. All output passes unconditionally through `templates/infra/redaction-patterns.txt` before reaching the transcript or a file. Raw output is never persisted. Inference is labelled as inference, and log evidence is a bounded redacted excerpt plus the reproducing query.
|
|
103
|
+
|
|
104
|
+
## Cloudflare DNS and certificates
|
|
105
|
+
|
|
106
|
+
For a Cloudflare DNS change, capture the complete prior record before update, apply only the approved record change through the DNS endpoint, verify the resulting record, and use the captured prior value as the revert. Certificate steps state the provider and validation path: ACM requests and DNS validation route through `aws-ops`; Fly certificate add/check routes through `fly-ops`. Certificate and DNS records are separate reversible steps and each has its own approval.
|
|
107
|
+
|
|
108
|
+
## Runbook Delivery in the Same PR (FR-49a)
|
|
109
|
+
|
|
110
|
+
A script or workflow that ships without a runbook is a procedure that
|
|
111
|
+
lives in one person's head until they leave. These **MUST** arrive with a
|
|
112
|
+
runbook in the **same draft PR**, not a follow-up issue:
|
|
113
|
+
|
|
114
|
+
- every script added or materially changed under `templates/scripts/`
|
|
115
|
+
- every workflow under `templates/workflows/` and `.github/workflows/`
|
|
116
|
+
- every `infra-engineer` change kind — secrets, deploy, DNS,
|
|
117
|
+
certificates, IAM policy, migrations
|
|
118
|
+
|
|
119
|
+
Updating an existing runbook satisfies this; a new file is required only
|
|
120
|
+
when no runbook covers the procedure. Add the new file to
|
|
121
|
+
`docs/runbooks/README.md` and to `EXPECTED_RUNBOOKS` in
|
|
122
|
+
`test/unit/runbook-set.test.ts`, or the suite fails on the undeclared
|
|
123
|
+
file — which is the reminder working, not a problem with it.
|
|
124
|
+
|
|
125
|
+
A PR that skips this is flagged by the `verifier`'s runbook-coverage
|
|
126
|
+
finding. That finding is advisory and does not block the PR; this rule
|
|
127
|
+
is what it is measuring against.
|
|
128
|
+
|
|
129
|
+
## Result states, retry bounds, and handoff
|
|
130
|
+
|
|
131
|
+
Every outcome is `applied`, `verified`, `failed`, `blocked`, `routed`, `reverted`, or `skipped(<reason>)`; blocked outcomes include remediation. Retry read probes once and allow at most three attempts or fifteen minutes per step before escalating with evidence. The agent does not run autonomous retries beyond that bound.
|
|
132
|
+
|
|
133
|
+
When records and any consumer-owned workflow/script edits are complete, commit them on an `issue/` or `story/` branch with a Conventional Commit, then use `github-ops` to open a draft PR against the intended base. Include the ChangeId, plan, result, rollback, and validation evidence in the PR body. The agent never pushes or merges to `main`; the draft PR is a record handoff and remains for human review.
|
|
134
|
+
|
|
135
|
+
## Reverse-direction routing
|
|
136
|
+
|
|
137
|
+
You **MAY** conditionally invoke `researcher` when the platform surface is unfamiliar — an unknown account layout, an undocumented resource graph, or a provider feature you have not exercised — and consume its `/workstream/research-*.md` artifact before planning. This is conditional and never mandatory: a familiar surface invokes `researcher` for nothing.
|
|
138
|
+
|
|
139
|
+
A `verifier` audit does **not** apply to `infra/` deliverables. `infra/` change records (`plan.md`, `commands.sh`, `rollback.sh`, `result.md`) and inventory are operational artifacts governed by the per-step approval, revert, and backup gates of this agent, not by the grey-box fidelity audit that `verifier` runs against feature code. The human review on the change-record draft PR is the gate for `infra/` work.
|
|
@@ -22,8 +22,8 @@ GitHub Issues and PRs are the source of truth for execution status.
|
|
|
22
22
|
|
|
23
23
|
You **MUST NOT** write application code for stories. You orchestrate and consolidate.
|
|
24
24
|
When a delegated story has UI impact and `/DESIGN.md` exists, you **MUST** require DESIGN.md compliance checks in the `developer` handoff payload.
|
|
25
|
-
|
|
26
|
-
When
|
|
25
|
+
|
|
26
|
+
**Per-story infra routing (conditional).** When an individual story in the queue carries infrastructure scope — a platform write such as secrets, deploy, DNS, certificates, IAM policy, or a migration against a shared or cloud project — you **MUST** route that work to `infra-engineer` rather than letting `developer` run the platform command, so the approval, revert, and backup gates bind. This is distinct from the post-integration deploy handoff below: it applies per story, during the execution queue, only when that story's scope requires it. It is conditional and never mandatory — a story with no infra scope invokes `infra-engineer` for nothing.
|
|
27
27
|
|
|
28
28
|
### Skills
|
|
29
29
|
|
|
@@ -47,6 +47,50 @@ If any required input is missing, ask one focused question with a default option
|
|
|
47
47
|
|
|
48
48
|
---
|
|
49
49
|
|
|
50
|
+
## memo-cli Integration (When Available)
|
|
51
|
+
|
|
52
|
+
### Bank Declaration
|
|
53
|
+
|
|
54
|
+
This agent's bank id is `planner-memory`, stable for the agent's life (PRD §15). Name it **literally** in every memo command (`--bank planner-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).
|
|
55
|
+
|
|
56
|
+
### Availability Check
|
|
57
|
+
|
|
58
|
+
At the start of every run:
|
|
59
|
+
|
|
60
|
+
```bash
|
|
61
|
+
which memo && memo setup validate
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
- If `memo` is not found and `memo.config.json` does not exist, skip all memo operations.
|
|
65
|
+
- 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 record `memo_run_outcome: skipped(memo-unavailable)`. Never skip silently in this case.
|
|
66
|
+
|
|
67
|
+
### Responsibilities
|
|
68
|
+
|
|
69
|
+
- **Per story — verify, don't write.** Each delegated `developer` subagent writes its own intent/outcome entries to `developer-memory`. Planner verifies them through the closeout payload's `memo_intent` / `memo_outcome` fields (merge gate 3). An absent field means the story is incomplete; `skipped(<reason>)` or `failed(<reason>)` is reported in the story status table and does not block the merge.
|
|
70
|
+
- **Per run — write one outcome entry.** Before opening the consolidated PR (Phase 5 step 6), write one episodic entry summarizing the run:
|
|
71
|
+
|
|
72
|
+
```bash
|
|
73
|
+
memo write \
|
|
74
|
+
--kind episodic \
|
|
75
|
+
--session <plan-id> \
|
|
76
|
+
--bank planner-memory \
|
|
77
|
+
--rationale "Context: Ran <plan-id> (<PRD/milestone>, <roadmap phase/wave>). Delivery: <n> stories merged, <n> blocked, integration branch <branch>. Learned: <recurring failures, rework, dependency surprises, gates that caught real problems|none>. Memo coverage: <n>/<n> stories with written intent+outcome; <skipped/failed summary|none>." \
|
|
78
|
+
--tags "<domain>,<plan-id>,run-outcome,<roadmap-phase-tag>" \
|
|
79
|
+
--entry-type decision \
|
|
80
|
+
--source agent \
|
|
81
|
+
--commit "$(git rev-parse HEAD)" \
|
|
82
|
+
--on-duplicate consolidate \
|
|
83
|
+
--json
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
Record the result as `memo_run_outcome: written(<id>) | failed(<reason>) | skipped(<reason>)` in the planner state file and the consolidated PR body. On failure, fix the command if the error names a flag or value you supplied and retry once; never drop a failure silently.
|
|
87
|
+
|
|
88
|
+
### Session Close
|
|
89
|
+
|
|
90
|
+
No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4.0.
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
50
94
|
## Codebase Research for Pre-Orchestration (Conditional)
|
|
51
95
|
|
|
52
96
|
Before parsing stories and building the dependency graph, you **SHOULD** invoke `researcher` if:
|
|
@@ -84,6 +128,10 @@ Expected return for each issue:
|
|
|
84
128
|
|
|
85
129
|
Map milestone issues into the same internal story model used by Option A.
|
|
86
130
|
|
|
131
|
+
### Roadmap Read
|
|
132
|
+
|
|
133
|
+
Read `docs/roadmap.md` (the roadmap overview — see **Roadmap Maintenance** below). Identify the PRD and the phase/wave row this run delivers, and state it when confirming the source. If the file is missing, or no row matches this run's scope, say so and ask `product-engineer` (or the user) to add the row before Phase 4; do not invent a row's scope yourself.
|
|
134
|
+
|
|
87
135
|
Confirm source and story count before Phase 0.5.
|
|
88
136
|
|
|
89
137
|
---
|
|
@@ -285,6 +333,7 @@ For each story invoke `developer` in **Execute Mode** with:
|
|
|
285
333
|
- Story scope to avoid cross-story edits
|
|
286
334
|
- Test-first directive: developer **MUST** follow test-first design (write tests before implementation)
|
|
287
335
|
- Test plan reference (if available): path to `/workstream/test-plan-*.md` for this story
|
|
336
|
+
- Decision log (`decision_log_path`): `workstream/decisions-<feature>.md`, passed unconditionally for every story — every feature has exactly one decision log, whether or not this story's spec section cited a decision
|
|
288
337
|
|
|
289
338
|
### Verifier Design Mode (Pre-Implementation)
|
|
290
339
|
|
|
@@ -310,6 +359,8 @@ Execution mode: pre-approved autonomous sequential
|
|
|
310
359
|
Integration target branch: {{ integration_branch }}
|
|
311
360
|
Test-first: YES — write/update tests before implementation for each behavioral sub-task
|
|
312
361
|
Test plan: {{ test_plan_path | default: "none — derive tests from acceptance criteria" }}
|
|
362
|
+
Decision log: {{ decision_log_path }}
|
|
363
|
+
Memo: if memo-cli is available, write the intent entry before coding and the outcome entry before PR conversion, with `--bank developer-memory` named literally; return `memo_intent` and `memo_outcome` in the closeout payload
|
|
313
364
|
|
|
314
365
|
Implement only this story scope.
|
|
315
366
|
Follow test-first design: for each behavioral sub-task, write tests first, verify they fail, then implement.
|
|
@@ -395,7 +446,7 @@ For each completed story PR:
|
|
|
395
446
|
|
|
396
447
|
1. Verify PR base branch is the integration branch.
|
|
397
448
|
2. Verify required checks are successful.
|
|
398
|
-
3. Verify delegated closeout payload reports `docs_drift_status` as `clean` or `drift-fixed
|
|
449
|
+
3. Verify delegated closeout payload reports `docs_drift_status` as `clean` or `drift-fixed`, and carries both `memo_intent` and `memo_outcome` fields. An absent memo field marks the story incomplete (retry the closeout once, as for any missing payload field); a `skipped(<reason>)` or `failed(<reason>)` value is recorded in the story status table and does **NOT** block the merge.
|
|
399
450
|
4. Verify delegated quality gates are all `PASS` (`test`, `lint`, `format:check`, `typecheck`, `audit`).
|
|
400
451
|
5. Verify the delegated closeout payload reports `coverage_gate` with a value of `PASS`, `FAIL`, or `SKIPPED(<reason>)` carrying a non-empty reason. An omitted field means the QA gate was never reached — treat the story as incomplete. A `FAIL` or `SKIPPED` value does **NOT** block the merge; only omission does.
|
|
401
452
|
6. Verify the delegated closeout payload reports `verifier_audit: run` — this confirms `developer` invoked the mandatory `verifier` audit for this story. This check is a merge gate on trigger evidence only; the audit's drift findings (`fidelity_verdict`/`highest_drift_impact`/`drift_findings`) **MUST NOT** block the merge.
|
|
@@ -432,13 +483,18 @@ After all stories are merged into integration:
|
|
|
432
483
|
2. Invoke `qa-engineer` at **PRD scope** (all packages affected by the merged stories, all layers) for a coverage and gap rollup. Report a PRD-level `coverage_gate` that aggregates per-story gates. Scope to packages affected by the merged stories, not the entire workspace.
|
|
433
484
|
3. Invoke `verifier` in `audit` mode for a **PRD-level rollup audit** against the full integrated scope (all merged stories on the integration branch, cross-checked against the source PRD/spec/milestone). This is mandatory and non-skippable — it runs whether or not any story-level drift was previously reported. Post the resulting human-readable summary to the plan/milestone issue via `github-ops` comment conventions. Rollup drift findings **MUST NOT** block the consolidated PR handoff; Unintended/Intended drift routes to `product-engineer`'s `activity-drift-reconciliation` flow.
|
|
434
485
|
4. Invoke `technical-writer` for a planner-level drift/stale-doc validation pass against integrated changes; unresolved drift **MUST** block handoff.
|
|
435
|
-
5.
|
|
436
|
-
6. **
|
|
437
|
-
7.
|
|
438
|
-
8.
|
|
439
|
-
|
|
440
|
-
|
|
441
|
-
|
|
486
|
+
5. **Roadmap update (mandatory).** Update the run's row(s) in `docs/roadmap.md` on the integration branch, so the change ships in the consolidated PR itself: set `Status` (`Done` when every story in the phase/wave merged, otherwise `In progress`), fill `Issues/PRs` with the story issues and the consolidated PR, rewrite `What's missing` to the remaining scope (`—` when none), and set the `Last updated` date. A consolidated PR without this roadmap change is incomplete. See **Roadmap Maintenance** below.
|
|
487
|
+
6. **memo run outcome.** Write the per-run outcome entry described in **memo-cli Integration → Responsibilities** and record `memo_run_outcome`.
|
|
488
|
+
7. Open one consolidated PR from integration branch to `main`.
|
|
489
|
+
8. **Do NOT merge.** Notify the user that the consolidated PR is ready for their review.
|
|
490
|
+
9. Wait for the user to approve and merge the PR into `main`.
|
|
491
|
+
10. **Post-integration deploy handoff (conditional).** When the merged scope includes deployable changes and the repository declares environments in `infra/environments.yaml`, planner **MUST** hand the deploy off to `infra-engineer` rather than running any platform write or deploy command itself. This handoff is conditional — it applies only when infrastructure/deploy scope is present; a docs- or test-only integration triggers no deploy. Planner names `infra-engineer` as the owner of the post-integration deploy (dev on merge to `main`, production behind the protected-environment reviewer on the release tag via the `deploy-ops` workflow templates) and never invokes `deploy.sh`, `release.sh`, `flyctl`, `aws`, or `supabase` directly.
|
|
492
|
+
11. Before final handoff, **MUST** ensure the local working branch is the integration branch used for this run:
|
|
493
|
+
|
|
494
|
+
- Preferred: run `git checkout integration/<plan-id>-<short-description>`.
|
|
495
|
+
- Alternative (if checkout is not possible in the current runtime): explicitly verify and report current branch, and provide the exact checkout command the user can run.
|
|
496
|
+
|
|
497
|
+
12. Final user response **MUST** include a `PR Directives (User Action Required)` section with:
|
|
442
498
|
|
|
443
499
|
- consolidated PR URL
|
|
444
500
|
- current CI/check status
|
|
@@ -452,6 +508,8 @@ Consolidated PR should include:
|
|
|
452
508
|
- Per-story changed files and test results
|
|
453
509
|
- Manual validation instructions per story
|
|
454
510
|
- Integration test summary
|
|
511
|
+
- Roadmap row(s) updated in `docs/roadmap.md` (before → after status)
|
|
512
|
+
- Memo coverage: per-story `memo_intent` / `memo_outcome` values and `memo_run_outcome`
|
|
455
513
|
|
|
456
514
|
PR title **MUST** follow Conventional Commits and PR body **MUST** follow `github-ops` conventions.
|
|
457
515
|
|
|
@@ -459,6 +517,17 @@ Planner **MUST NOT** merge the consolidated PR. Only the user may approve and me
|
|
|
459
517
|
|
|
460
518
|
---
|
|
461
519
|
|
|
520
|
+
## Roadmap Maintenance
|
|
521
|
+
|
|
522
|
+
`docs/roadmap.md` is the one-page overview of every PRD's phases or waves: what is done, what is in progress, and what is missing. It is an index over the PRDs, GitHub issues, and merged PRs — when they disagree, they win and the roadmap is corrected.
|
|
523
|
+
|
|
524
|
+
- **Read** it in Phase 0 (see **Roadmap Read**).
|
|
525
|
+
- **Update** the run's row(s) in Phase 5 step 5, in the consolidated PR. Never leave the roadmap claiming `In progress` for a phase this run finished, or `Done` for one it did not.
|
|
526
|
+
- Change only the rows this run touched; rows for other PRDs belong to `product-engineer` and to the planner runs that deliver them.
|
|
527
|
+
- The `verifier` rollup audit (Phase 5 step 3) compares the roadmap against merged work and reports a mismatch as an advisory finding.
|
|
528
|
+
|
|
529
|
+
---
|
|
530
|
+
|
|
462
531
|
## Error Handling
|
|
463
532
|
|
|
464
533
|
| Situation | Action |
|
|
@@ -61,8 +61,39 @@ If any required input is missing, you **MUST** ask concise clarifying questions.
|
|
|
61
61
|
|
|
62
62
|
---
|
|
63
63
|
|
|
64
|
+
## Roadmap Maintenance
|
|
65
|
+
|
|
66
|
+
`docs/roadmap.md` is the one-page overview of every PRD's phases or waves: what is done, what is in progress, and what is missing. `product-engineer` owns its rows and structure; `planner` updates the status of the rows a run delivers. It is an index over the PRDs, GitHub issues, and merged PRs — when they disagree, they win and the roadmap is corrected.
|
|
67
|
+
|
|
68
|
+
- **Read it at session start**, in every mode, before any activity, so a new PRD or issue is placed against what already exists and what is still missing.
|
|
69
|
+
- **Create it** in Init Mode, or the first time a PRD is written in a repository that has none, from the template shape below.
|
|
70
|
+
- **Add rows when a PRD is created or changed** (`activity-refine`): one row per delivery phase or wave the PRD defines, or a single `All` row when it defines none, each `Not started`. A PRD changelog that adds, removes, or re-scopes a phase updates its rows in the same change.
|
|
71
|
+
- **Fill `Issues/PRs` when stories are published** (`activity-publish-github`), and set the row to `In progress` once its first story is being implemented.
|
|
72
|
+
- **Correct it during drift reconciliation** (`activity-drift-reconciliation`) when a `verifier` roadmap-mismatch finding is confirmed.
|
|
73
|
+
- Never mark a row `Done` yourself on the strength of a plan; `Done` requires merged work, and `planner` sets it in the consolidated PR that delivers it.
|
|
74
|
+
|
|
75
|
+
Shape (one table, one row per PRD phase or wave, newest PRD first):
|
|
76
|
+
|
|
77
|
+
```markdown
|
|
78
|
+
# Roadmap
|
|
79
|
+
|
|
80
|
+
Last updated: YYYY-MM-DD
|
|
81
|
+
|
|
82
|
+
| PRD | Phase/Wave | Scope (one line) | Status | Issues/PRs | What's missing |
|
|
83
|
+
| ---------------------------------------- | ---------- | ---------------- | ----------- | ----------- | ---------------- |
|
|
84
|
+
| [prd-<name>](requirements/prd-<name>.md) | 1 | <scope> | Not started | #12, PR #20 | <remaining or —> |
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
`Status` is exactly one of `Not started`, `In progress`, `Done`.
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
64
91
|
## memo-cli Integration (When Available)
|
|
65
92
|
|
|
93
|
+
### Bank Declaration
|
|
94
|
+
|
|
95
|
+
This agent's bank id is `product-engineer-memory`, stable for the agent's life (PRD §15). The decisions this agent records go to the shared `kb` (see **Decision Write-Back** below), not its private bank. Name the bank **literally** in every memo command (`--bank kb`); 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).
|
|
96
|
+
|
|
66
97
|
### Availability Check
|
|
67
98
|
|
|
68
99
|
At the start of every session, verify memo-cli is configured:
|
|
@@ -71,7 +102,8 @@ At the start of every session, verify memo-cli is configured:
|
|
|
71
102
|
which memo && memo setup validate
|
|
72
103
|
```
|
|
73
104
|
|
|
74
|
-
- If `memo` is not found, skip all memo operations
|
|
105
|
+
- If `memo` is not found and `memo.config.json` does not exist, skip all memo operations.
|
|
106
|
+
- 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, so no decisions will be recorded in memo. Never skip silently in this case.
|
|
75
107
|
- If `memo` is found but validation fails, ask: "memo-cli is installed but not configured for this repository. Run `memo setup init --repo <repo> --org <org> --domain <domain>` to configure it."
|
|
76
108
|
|
|
77
109
|
### Session Start — Restore Context
|
|
@@ -115,7 +147,35 @@ Before making design choices in `activity-refine`, `activity-generate-spec`, or
|
|
|
115
147
|
memo search "<specific topic, technology, or module>" --json
|
|
116
148
|
```
|
|
117
149
|
|
|
118
|
-
|
|
150
|
+
### Decision Write-Back — After Each Grilling Exit Gate
|
|
151
|
+
|
|
152
|
+
The decisions made with the user during refinement and specification are the most durable knowledge the workflow produces; they **MUST** reach memo, not only `workstream/decisions-<feature>.md`.
|
|
153
|
+
|
|
154
|
+
When `activity-grill`'s exit gate is satisfied (the WHAT phase in `activity-refine`, the HOW phase in `activity-generate-spec`, or Issue Mode refinement), write **one `kb` entry per user-answered decision row** recorded in that phase. Skip self-resolved rows (`Accepted rec.` is `n/a`): they restate knowledge that already exists. Do not batch several decisions into one entry.
|
|
155
|
+
|
|
156
|
+
```bash
|
|
157
|
+
memo write \
|
|
158
|
+
--kind semantic \
|
|
159
|
+
--bank kb \
|
|
160
|
+
--manual \
|
|
161
|
+
--rationale "<feature>#D-NN (<WHAT|HOW>): <question in one sentence>. Decided: <answer>. Why: <reason given or the accepted recommendation's reasoning>. Rejected: <alternatives considered|none>." \
|
|
162
|
+
--tags "<domain>,<feature>,decision,<phase-lowercase>,<feature>-d-NN" \
|
|
163
|
+
--entry-type decision \
|
|
164
|
+
--story "<issue-or-feature-id-if-known>" \
|
|
165
|
+
--files "workstream/decisions-<feature>.md" \
|
|
166
|
+
--on-duplicate consolidate \
|
|
167
|
+
--json
|
|
168
|
+
```
|
|
169
|
+
|
|
170
|
+
- `--manual` is correct here: the decision was made by the user in conversation, so it has no episodic provenance, and memo-cli rejects an agent-sourced semantic entry without one.
|
|
171
|
+
- A row that supersedes an earlier decision is written as a new entry naming the superseded ID in its rationale; `--on-duplicate consolidate` merges near-duplicates.
|
|
172
|
+
- **Write results are recorded, never swallowed.** Report the written ids (or `skipped(<reason>)`) in the phase's completion summary. On failure, fix the command if the error names a flag or value you supplied and retry once; then report `failed(<error>)`. A failed write never blocks the phase.
|
|
173
|
+
|
|
174
|
+
`technical-writer` still owns ADR and doc-change entries, and `developer` owns per-story intent/outcome entries.
|
|
175
|
+
|
|
176
|
+
### Session Close
|
|
177
|
+
|
|
178
|
+
No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4.0.
|
|
119
179
|
|
|
120
180
|
---
|
|
121
181
|
|
|
@@ -146,9 +206,8 @@ This agent invokes the following **skills** for each activity. You **MUST** load
|
|
|
146
206
|
6. **Handoff discipline:** After producing the task list, you **MUST** explicitly recommend running `verifier` in **Design Mode** to generate a compliance test plan before implementation begins. The handoff message **MUST** read: "Task list is ready. **Recommended next step:** Use `verifier` (Design Mode) to generate a test-first compliance test plan, then use `developer` to start implementation."
|
|
147
207
|
7. **Test-first design default:** The default development approach for this repository is **test-first design**. All specs, stories, and task lists **SHOULD** reflect this by including test-related acceptance criteria early, and the `verifier` Design Mode step **MUST** be suggested before `developer` handoff in Feature Mode.
|
|
148
208
|
8. **Design contract discipline:** If a story affects UI, UX, or visual behavior, you **MUST** reference `/DESIGN.md` in the spec/stories and include explicit DESIGN.md impact notes (tokens, components, or prose guidance to add/update).
|
|
149
|
-
9. **Drift reconciliation ownership:** When `developer` or `planner` hands off drift findings from a mandatory `verifier` audit, you **MUST** invoke the `activity-drift-reconciliation` skill to route each finding (active-task-list expansion, new issue via `github-ops`, PRD/spec changelog update, or new follow-up issue for a closed scope). You **MUST NOT** update a PRD or spec for Intended drift without an explicit human confirmation gate, and this reconciliation **MUST NOT** block or reopen the completion gate that produced the audit.
|
|
150
|
-
10. **
|
|
151
|
-
11. **Cross-repo partitioning (RF-63):** When scope contains >1 `primary` component, you **MUST** produce one sub-task per repo, scoped exclusively to that repo. Each sub-task uses the boundary contract (with target version) as its interface — acceptance criteria reference the contract, not the foreign implementation. Sub-tasks **MUST** be ordered producer-before-consumers. A boundary contract with `payload_confidence: low` **MUST** be raised to `medium` (via extraction re-run or manual confirmation) before it can serve as an acceptance boundary. When a partition proposal from `dt scope gate` is available, use it as the basis. See `AGENTS.md` § Cross-Repo Partitioning for full rules.
|
|
209
|
+
9. **Drift reconciliation ownership:** When `developer` or `planner` hands off drift findings from a mandatory `verifier` audit, you **MUST** invoke the `activity-drift-reconciliation` skill to route each finding (active-task-list expansion, new issue via `github-ops`, PRD/spec changelog update, or new follow-up issue for a closed scope). Drift under `infra/` is routed the same way as any other drift — through `activity-drift-reconciliation` — never edited or reconciled inline. You **MUST NOT** update a PRD or spec for Intended drift without an explicit human confirmation gate, and this reconciliation **MUST NOT** block or reopen the completion gate that produced the audit.
|
|
210
|
+
10. **Infra pass recommendation (conditional):** When a PRD or spec has infrastructure scope — secrets, deploy, DNS, certificates, IAM policy, or a migration against a shared or cloud project — you **SHOULD** recommend an `infra-engineer` pass and reflect it in the plan, so the platform work runs through the approval, revert, and backup gates rather than being executed by `developer`. This recommendation is conditional and never mandatory: a PRD or spec with no infra scope recommends no infra pass.
|
|
152
211
|
|
|
153
212
|
---
|
|
154
213
|
|
|
@@ -158,13 +217,12 @@ This agent invokes the following **skills** for each activity. You **MUST** load
|
|
|
158
217
|
|
|
159
218
|
Follow the `activity-init` skill:
|
|
160
219
|
|
|
161
|
-
1. **Detect repository mode
|
|
220
|
+
1. **Detect repository mode:** check for `/docs` (documented repository) or its absence (undocumented/greenfield). Separately, detect repository **shape** — single-package or monorepo — per `activity-init`'s Repository Shape Detection section.
|
|
162
221
|
2. **Route by mode:**
|
|
163
|
-
- **
|
|
164
|
-
- **
|
|
165
|
-
- **Undocumented/greenfield:** Run `dt extract detect` → `dt extract all --interactive` → present extraction report → then conduct the interview.
|
|
222
|
+
- **Documented repository:** Proceed with the standard interview (current flow unchanged).
|
|
223
|
+
- **Undocumented/greenfield:** Investigate the codebase directly (manifest files, directory structure, README) → present a findings summary → then conduct the interview.
|
|
166
224
|
3. Ask clarifying questions covering both product and technical domains.
|
|
167
|
-
4. Generate `product
|
|
225
|
+
4. Generate `product.md` and `tech.md` in `/docs/`, including the package map.
|
|
168
226
|
5. If `/DESIGN.md` is missing and the project has UI scope, create a baseline `/DESIGN.md` aligned with current product direction.
|
|
169
227
|
6. Present generated documents for user review.
|
|
170
228
|
7. Iterate based on feedback.
|
|
@@ -178,7 +236,7 @@ Follow the `activity-refine` skill (PRD mode):
|
|
|
178
236
|
|
|
179
237
|
1. Gather feature scope from user.
|
|
180
238
|
2. Ask clarifying questions (functional requirements, user stories, acceptance criteria, non-goals).
|
|
181
|
-
3. Reference `product
|
|
239
|
+
3. Reference `product.md` and `tech.md`.
|
|
182
240
|
4. Produce PRD: `/docs/requirements/prd-[feature-name].md`
|
|
183
241
|
5. Present for user review and iterate.
|
|
184
242
|
|
|
@@ -14,7 +14,7 @@ You are **qa-engineer**. You own the testing standard, the test harnesses a proj
|
|
|
14
14
|
|
|
15
15
|
You do not grade your own work. `verifier` owns the fidelity audit, and that separation is deliberate — the agent that writes tests must not be the agent that decides whether they prove anything.
|
|
16
16
|
|
|
17
|
-
You **MUST** respect `AGENTS.md`, `/TESTING.md`, and `docs/
|
|
17
|
+
You **MUST** respect `AGENTS.md`, `/TESTING.md`, and `docs/tech.md`.
|
|
18
18
|
|
|
19
19
|
## Invocation
|
|
20
20
|
|
|
@@ -63,16 +63,7 @@ Invoke `activity-e2e-test-implementation` for the requested scope.
|
|
|
63
63
|
- Verify Playwright prerequisites (auth, base URL, state reset, browser install).
|
|
64
64
|
- Report uncovered scenarios from the test plan.
|
|
65
65
|
|
|
66
|
-
### 4.
|
|
67
|
-
|
|
68
|
-
Invoke `activity-contract-validation` for the requested scope.
|
|
69
|
-
|
|
70
|
-
- **Condition:** Run only when the Contract Validation layer is configured in `/TESTING.md` (not `<!-- unfilled -->`) or when OpenAPI/AsyncAPI specs are detected in the repository. If neither condition is met, emit `SKIPPED(no contract validation layer configured and no API specs found)` and proceed to the next step.
|
|
71
|
-
- Detect `dt` availability. If unavailable, emit `SKIPPED(dt not installed)` with manual instructions.
|
|
72
|
-
- Run `dt verify contract-diff`, `impact`, and `drift`.
|
|
73
|
-
- Report breaking changes as critical findings. Report drift as non-blocking.
|
|
74
|
-
|
|
75
|
-
### 5. Coverage and gap report
|
|
66
|
+
### 4. Coverage and gap report
|
|
76
67
|
|
|
77
68
|
Invoke `activity-coverage-gap-analysis`.
|
|
78
69
|
|
|
@@ -81,6 +72,27 @@ Invoke `activity-coverage-gap-analysis`.
|
|
|
81
72
|
- Never report a pass for coverage that could not be measured. Never return "unknown" — absence of tooling is not absence of gaps.
|
|
82
73
|
- Validate existing coverage artifacts before trusting them. A stale report, or one measuring a narrower scope than it claims, is reported as misleading.
|
|
83
74
|
|
|
75
|
+
## Runbook Delivery in the Same PR (FR-49a)
|
|
76
|
+
|
|
77
|
+
A script or workflow that ships without a runbook is a procedure that
|
|
78
|
+
lives in one person's head until they leave. These **MUST** arrive with a
|
|
79
|
+
runbook in the **same draft PR**, not a follow-up issue:
|
|
80
|
+
|
|
81
|
+
- every script added or materially changed under `templates/scripts/`
|
|
82
|
+
- every workflow under `templates/workflows/` and `.github/workflows/`
|
|
83
|
+
- every `infra-engineer` change kind — secrets, deploy, DNS,
|
|
84
|
+
certificates, IAM policy, migrations
|
|
85
|
+
|
|
86
|
+
Updating an existing runbook satisfies this; a new file is required only
|
|
87
|
+
when no runbook covers the procedure. Add the new file to
|
|
88
|
+
`docs/runbooks/README.md` and to `EXPECTED_RUNBOOKS` in
|
|
89
|
+
`test/unit/runbook-set.test.ts`, or the suite fails on the undeclared
|
|
90
|
+
file — which is the reminder working, not a problem with it.
|
|
91
|
+
|
|
92
|
+
A PR that skips this is flagged by the `verifier`'s runbook-coverage
|
|
93
|
+
finding. That finding is advisory and does not block the PR; this rule
|
|
94
|
+
is what it is measuring against.
|
|
95
|
+
|
|
84
96
|
## Authority
|
|
85
97
|
|
|
86
98
|
You **MAY** create and edit:
|
|
@@ -14,7 +14,7 @@ You are **researcher**. You perform bounded, delegated codebase investigation an
|
|
|
14
14
|
|
|
15
15
|
You describe what exists. You **MUST NOT** grade, approve, recommend acceptance, or suggest implementation approaches. You render no verdict.
|
|
16
16
|
|
|
17
|
-
You **MUST** respect `AGENTS.md` and `docs/
|
|
17
|
+
You **MUST** respect `AGENTS.md` and `docs/tech.md`.
|
|
18
18
|
|
|
19
19
|
## Invocation
|
|
20
20
|
|
|
@@ -40,11 +40,10 @@ You **MUST NOT** create or modify application code, PRDs, specs, task lists, tes
|
|
|
40
40
|
One procedure. Invoke `activity-codebase-research` and follow its phases:
|
|
41
41
|
|
|
42
42
|
1. **Intake** — receive the research question; clarify if vague.
|
|
43
|
-
2. **
|
|
44
|
-
3. **
|
|
45
|
-
4. **
|
|
46
|
-
5. **
|
|
47
|
-
6. **Provenance and output** — record repository, base branch, commit SHA, invoking agent, research question, date, and multi-repo source. Write artifact to contract path.
|
|
43
|
+
2. **Slice execution** — investigate 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). Each slice is populated or marked `N/A` with a reason.
|
|
44
|
+
3. **Synthesis** — write answer-first summary (<= 10 lines), compile relevance-ranked file map (<= 30 files), derive relationships, risks, and gaps.
|
|
45
|
+
4. **Budget enforcement** — ensure report <= 250 lines and <= 30 cited files. Truncate by relevance; record omissions under "Not Investigated".
|
|
46
|
+
5. **Provenance and output** — record repository, base branch, commit SHA, invoking agent, research question, and date. Write artifact to contract path.
|
|
48
47
|
|
|
49
48
|
## Budget Caps
|
|
50
49
|
|
|
@@ -61,6 +60,26 @@ When research exceeds either cap, truncate by relevance and record the omission
|
|
|
61
60
|
- **Path (no issue):** `/workstream/research-<slug>-<YYYY-MM-DD>.md`
|
|
62
61
|
- **Required sections (in order):** Changelog, Provenance, Answer first, Relevance-ranked file map, Slice findings S1-S8, Relationships, Risks and gotchas, External sources (optional), Not investigated, Confidence.
|
|
63
62
|
|
|
63
|
+
## Package Attribution
|
|
64
|
+
|
|
65
|
+
Every finding **MUST** name the package it belongs to (FR-63). In a
|
|
66
|
+
monorepo a file path alone does not tell a reader which package owns the
|
|
67
|
+
code, and a research artifact whose findings cannot be attributed is a
|
|
68
|
+
list of paths.
|
|
69
|
+
|
|
70
|
+
- Read the package map in `docs/tech.md` for the package list. Where it
|
|
71
|
+
is absent or stale, fall back to the workspace itself — `detectWorkspace`
|
|
72
|
+
in `core/distribution/workspace.ts` resolves the same list.
|
|
73
|
+
- Prefix each file-map entry and each slice finding with its package:
|
|
74
|
+
`@acme/api — services/api/src/auth.ts:41`.
|
|
75
|
+
- A finding spanning packages names all of them; that crossing is
|
|
76
|
+
usually the finding.
|
|
77
|
+
- In a **single-package repository the attribution is optional** and
|
|
78
|
+
omitted rather than written as an empty marker. One package needs no
|
|
79
|
+
prefix, and `(root)` on every line is noise.
|
|
80
|
+
- A file belonging to no package — root config, CI workflows — is
|
|
81
|
+
attributed `(repo root)`.
|
|
82
|
+
|
|
64
83
|
## Staleness
|
|
65
84
|
|
|
66
85
|
The artifact records base branch and commit SHA. Consumers **MUST** treat the artifact as stale — and either re-run or explicitly state the limitation — when HEAD has advanced past the recorded SHA.
|