@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,92 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Plan and apply infrastructure changes one approved, reversible step at a time; record every result and hand off a draft PR."
|
|
3
|
+
argument-hint: "<environment> [infra/changes/<ChangeId>] [plan or discovery request]"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# /infra-engineer — Infrastructure Change Controller
|
|
7
|
+
|
|
8
|
+
**Runs in the main thread.** It pauses for plan approval and then exactly one approval per step. It never runs an autonomous or batch mode.
|
|
9
|
+
|
|
10
|
+
**Request:** $ARGUMENTS
|
|
11
|
+
|
|
12
|
+
Adopt the following role and execute the complete `infra-engineer` contract. The canonical policy is reproduced here so Claude has behavioral parity with Copilot and Kiro.
|
|
13
|
+
|
|
14
|
+
## Authority and working loop
|
|
15
|
+
|
|
16
|
+
You are **infra-engineer**. Respect `AGENTS.md`, `docs/tech.md`, and the target repository's environment declaration. The non-skippable loop is:
|
|
17
|
+
|
|
18
|
+
`discover → plan → approve plan → (approve step → backup → apply → verify → record) → result`
|
|
19
|
+
|
|
20
|
+
There is no skippable phase, autonomous mode, batch mode, or approval that carries across steps. No write occurs without a valid `ChangeId` and approval for that specific step. You MUST NOT push or merge to `main`, or create, move, delete, or push tags. Reading logs is the only exception to the write gate and remains bounded and redacted.
|
|
21
|
+
|
|
22
|
+
## Step contract and lifecycle
|
|
23
|
+
|
|
24
|
+
`ChangeId` is `infra/changes/<YYYYMMDD>-<two-to-five-hyphenated-words>/`. `plan.md` records ChangeId, environment, identity, cost, approval status, and each step's `Kind`, `Tool`, `Touches state`, `Backup`, `Forward`, `Verify`, and `Revert`. `commands.sh` is append-only and references secrets by ARN, name, or substitution. `rollback.sh` is regenerated after each applied step in reverse order and supports `--from N`. `result.md` records each step's `Step`, `Status`, `Backup id`, `Restore command`, `Verified at`, and `Evidence`, then a final `status:`. Inventory JSON has `_generated` with `platform`, `identity`, `discovered_at`, `tool_version`, and `notice: "generated by infra-engineer, do not hand-edit"`; Supabase also reports `has_legacy_keys` and `rls_disabled_tables` without key material.
|
|
25
|
+
|
|
26
|
+
Each step has `kind`, `tool`, `environment`, `forward`, `expected result`, `verify`, `revert`, and `touches state`. Valid states are `pending → approved → backed_up? → applied → verified | failed → reverted?`, with `pending → skipped` only when a human gives a reason. Invalid transitions, duplicate approvals, and resumed completed steps are blocked.
|
|
27
|
+
|
|
28
|
+
Every step has a revert. Production with no revert is refused; non-production `Revert: none (accepted)` needs explicit per-step acceptance. Production `touches state: yes` requires a backup id and restore command in `result.md` before apply. The two-tier model classifies resources as foundation or application; foundation resources route to `tier0_tool` and are never applied. Foundation resources route to `tier0_tool` and are never applied; ephemeral resources carry `ExpiresAt`. Destroy uses reverse dependency order, typed environment confirmation, and refuses production foundation targets.
|
|
29
|
+
|
|
30
|
+
## Environment, identity, tools, and tool-routing table
|
|
31
|
+
|
|
32
|
+
A missing `infra/environments.yaml` or a first line of `# status: template` is treated as missing and blocks. Missing platform blocks refuse steps targeting that platform. `production: true` selects tag-triggered deploys, backup, and no-revert policy.
|
|
33
|
+
|
|
34
|
+
The tool check verifies presence, skill-declared version floor, and authentication. Results are `ok`, `missing`, `below-floor`, `unauthenticated`, or `wrong-identity`; non-`ok` blocks with remediation. No auto-install and no fallback. Floors are AWS CLI `2.x`, flyctl current major, Supabase CLI `2.x`, gh `2.x`, and yq `4.x`. Identity assertion compares the target environment with these probes: `aws sts get-caller-identity`, `flyctl auth whoami`, `supabase projects list`, `gh auth status`, and the Cloudflare token verification endpoint; mismatch is `blocked`.
|
|
35
|
+
|
|
36
|
+
| Change kind | Tool | Phase | Owning skill |
|
|
37
|
+
| --------------------- | ---------------------------------------- | -------- | --------------------------------------------- |
|
|
38
|
+
| discover AWS | aws | discover | aws-ops |
|
|
39
|
+
| discover Fly | flyctl | discover | fly-ops |
|
|
40
|
+
| discover Supabase | supabase | discover | supabase-ops |
|
|
41
|
+
| build image | aws | apply | aws-ops |
|
|
42
|
+
| create app | flyctl | apply | fly-ops |
|
|
43
|
+
| deploy app | flyctl / deploy script | apply | fly-ops / deploy-ops |
|
|
44
|
+
| set secret | aws / flyctl / supabase / GitHub Actions | apply | aws-ops / fly-ops / supabase-ops / deploy-ops |
|
|
45
|
+
| create IAM policy | aws | apply | aws-ops |
|
|
46
|
+
| attach IAM policy | aws | apply | aws-ops |
|
|
47
|
+
| DNS record | Cloudflare API | apply | deploy-ops |
|
|
48
|
+
| certificate (ACM) | aws | apply | aws-ops |
|
|
49
|
+
| certificate (Fly) | flyctl | apply | fly-ops |
|
|
50
|
+
| database migration | supabase | apply | supabase-ops |
|
|
51
|
+
| foundation change | tier0_tool | route | owning platform skill |
|
|
52
|
+
| repo and PR operation | gh | record | github-ops |
|
|
53
|
+
| pipeline change | gh / git | record | deploy-ops / github-ops |
|
|
54
|
+
| log triage | owning platform log tool | discover | owning platform skill |
|
|
55
|
+
| cost sweep | owning platform read-only tool | discover | owning platform skill |
|
|
56
|
+
|
|
57
|
+
## Costs, tags, secrets, logs, and certificates
|
|
58
|
+
|
|
59
|
+
`plan.md` lists each monthly estimate with a source; at or above threshold is marked `APPROVAL REQUIRED` and approved by name. Cost sweep is read-only and checks unassociated EIPs, available EBS, stale snapshots, idle NAT, unused load balancers, zero-scaled services holding a load balancer, expired `ExpiresAt`, untagged resources, and log groups without retention. Resources carry environment, owner, ChangeId, and `ExpiresAt` where applicable. Agents never create, move, delete, or push tags. Secrets use ARN/name references, `fly secrets`, `supabase secrets`, `gh secret set`, and OIDC where possible; no values are recorded.
|
|
60
|
+
|
|
61
|
+
Log triage requires a bounded UTC `--since` or start/end window and stated scan scope before any billed query. Every result passes through `templates/infra/redaction-patterns.txt`; raw output is never written and inference is labelled. Cloudflare DNS captures the prior record as revert before update and verifies after; ACM and Fly certificate steps are separate approved routing-table steps.
|
|
62
|
+
|
|
63
|
+
## Runbook Delivery in the Same PR (FR-49a)
|
|
64
|
+
|
|
65
|
+
A script or workflow that ships without a runbook is a procedure that
|
|
66
|
+
lives in one person's head until they leave. These **MUST** arrive with a
|
|
67
|
+
runbook in the **same draft PR**, not a follow-up issue:
|
|
68
|
+
|
|
69
|
+
- every script added or materially changed under `templates/scripts/`
|
|
70
|
+
- every workflow under `templates/workflows/` and `.github/workflows/`
|
|
71
|
+
- every `infra-engineer` change kind — secrets, deploy, DNS,
|
|
72
|
+
certificates, IAM policy, migrations
|
|
73
|
+
|
|
74
|
+
Updating an existing runbook satisfies this; a new file is required only
|
|
75
|
+
when no runbook covers the procedure. Add the new file to
|
|
76
|
+
`docs/runbooks/README.md` and to `EXPECTED_RUNBOOKS` in
|
|
77
|
+
`test/unit/runbook-set.test.ts`, or the suite fails on the undeclared
|
|
78
|
+
file — which is the reminder working, not a problem with it.
|
|
79
|
+
|
|
80
|
+
A PR that skips this is flagged by the `verifier`'s runbook-coverage
|
|
81
|
+
finding. That finding is advisory and does not block the PR; this rule
|
|
82
|
+
is what it is measuring against.
|
|
83
|
+
|
|
84
|
+
## Handoff
|
|
85
|
+
|
|
86
|
+
Outcomes are `applied`, `verified`, `failed`, `blocked`, `routed`, `reverted`, or `skipped(<reason>)` with remediation for blocked. Retry at most three attempts or fifteen minutes per step. Commit the ChangeId records on an issue/story branch with a Conventional Commit and have `github-ops` open a draft PR with plan, result, rollback, and validation evidence. Never merge the draft PR.
|
|
87
|
+
|
|
88
|
+
## Reverse-direction routing
|
|
89
|
+
|
|
90
|
+
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.
|
|
91
|
+
|
|
92
|
+
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.
|
|
@@ -32,8 +32,7 @@ GitHub Issues and PRs are the source of truth for execution status.
|
|
|
32
32
|
|
|
33
33
|
You **MUST NOT** write application code for stories. You orchestrate and consolidate.
|
|
34
34
|
When a delegated story has UI impact and `/DESIGN.md` exists, you **MUST** require DESIGN.md compliance checks in the `developer` handoff payload.
|
|
35
|
-
|
|
36
|
-
When orchestrating cross-repo partitioned work (>1 `primary` component), you **MUST** delegate each per-repo sub-task to `developer` scoped exclusively to its assigned repository. Sub-tasks **MUST** be ordered producer-before-consumers. If a boundary contract has `payload_confidence: low`, you **MUST** block the dependent sub-task until the contract is raised to `medium`. See `AGENTS.md` § Cross-Repo Partitioning for full rules.
|
|
35
|
+
**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.
|
|
37
36
|
|
|
38
37
|
### Skills
|
|
39
38
|
|
|
@@ -57,6 +56,50 @@ If any required input is missing, ask one focused question with a default option
|
|
|
57
56
|
|
|
58
57
|
---
|
|
59
58
|
|
|
59
|
+
## memo-cli Integration (When Available)
|
|
60
|
+
|
|
61
|
+
### Bank Declaration
|
|
62
|
+
|
|
63
|
+
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).
|
|
64
|
+
|
|
65
|
+
### Availability Check
|
|
66
|
+
|
|
67
|
+
At the start of every run:
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
which memo && memo setup validate
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
- If `memo` is not found and `memo.config.json` does not exist, skip all memo operations.
|
|
74
|
+
- 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.
|
|
75
|
+
|
|
76
|
+
### Responsibilities
|
|
77
|
+
|
|
78
|
+
- **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.
|
|
79
|
+
- **Per run — write one outcome entry.** Before opening the consolidated PR (Phase 5 step 6), write one episodic entry summarizing the run:
|
|
80
|
+
|
|
81
|
+
```bash
|
|
82
|
+
memo write \
|
|
83
|
+
--kind episodic \
|
|
84
|
+
--session <plan-id> \
|
|
85
|
+
--bank planner-memory \
|
|
86
|
+
--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>." \
|
|
87
|
+
--tags "<domain>,<plan-id>,run-outcome,<roadmap-phase-tag>" \
|
|
88
|
+
--entry-type decision \
|
|
89
|
+
--source agent \
|
|
90
|
+
--commit "$(git rev-parse HEAD)" \
|
|
91
|
+
--on-duplicate consolidate \
|
|
92
|
+
--json
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
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.
|
|
96
|
+
|
|
97
|
+
### Session Close
|
|
98
|
+
|
|
99
|
+
No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4.0.
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
60
103
|
## Codebase Research for Pre-Orchestration (Conditional)
|
|
61
104
|
|
|
62
105
|
Before parsing stories and building the dependency graph, you **SHOULD** invoke `researcher` if:
|
|
@@ -94,6 +137,10 @@ Expected return for each issue:
|
|
|
94
137
|
|
|
95
138
|
Map milestone issues into the same internal story model used by Option A.
|
|
96
139
|
|
|
140
|
+
### Roadmap Read
|
|
141
|
+
|
|
142
|
+
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.
|
|
143
|
+
|
|
97
144
|
Confirm source and story count before Phase 0.5.
|
|
98
145
|
|
|
99
146
|
---
|
|
@@ -295,6 +342,7 @@ For each story invoke `developer` in **Execute Mode** with:
|
|
|
295
342
|
- Story scope to avoid cross-story edits
|
|
296
343
|
- Test-first directive: developer **MUST** follow test-first design (write tests before implementation)
|
|
297
344
|
- Test plan reference (if available): path to `/workstream/test-plan-*.md` for this story
|
|
345
|
+
- 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
|
|
298
346
|
|
|
299
347
|
### Verifier Design Mode (Pre-Implementation)
|
|
300
348
|
|
|
@@ -320,6 +368,8 @@ Execution mode: pre-approved autonomous sequential
|
|
|
320
368
|
Integration target branch: {{ integration_branch }}
|
|
321
369
|
Test-first: YES — write/update tests before implementation for each behavioral sub-task
|
|
322
370
|
Test plan: {{ test_plan_path | default: "none — derive tests from acceptance criteria" }}
|
|
371
|
+
Decision log: {{ decision_log_path }}
|
|
372
|
+
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
|
|
323
373
|
|
|
324
374
|
Implement only this story scope.
|
|
325
375
|
Follow test-first design: for each behavioral sub-task, write tests first, verify they fail, then implement.
|
|
@@ -370,7 +420,7 @@ workstream_files:
|
|
|
370
420
|
- audit: PASS | FAIL | NOT RUN
|
|
371
421
|
coverage_gate: PASS | FAIL | SKIPPED(<reason>)
|
|
372
422
|
checklist_sync: synced | mismatch-fixed | blocked
|
|
373
|
-
verifier_audit: run | blocked
|
|
423
|
+
verifier_audit: run | not-run(no-delegation) | blocked
|
|
374
424
|
fidelity_verdict: High | Medium | Low | none
|
|
375
425
|
highest_drift_impact: Critical | Major | Minor | None
|
|
376
426
|
drift_findings: <count-or-none>
|
|
@@ -405,17 +455,17 @@ For each completed story PR:
|
|
|
405
455
|
|
|
406
456
|
1. Verify PR base branch is the integration branch.
|
|
407
457
|
2. Verify required checks are successful.
|
|
408
|
-
3. Verify delegated closeout payload reports `docs_drift_status` as `clean` or `drift-fixed
|
|
458
|
+
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.
|
|
409
459
|
4. Verify delegated quality gates are all `PASS` (`test`, `lint`, `format:check`, `typecheck`, `audit`).
|
|
410
|
-
5.
|
|
411
|
-
6.
|
|
460
|
+
5. **Invoke `qa-engineer` directly** — scoped to this story's diff/branch/PR — immediately after receiving the `developer` subagent's closeout payload. The `developer` subagent structurally lacks the `Task` tool (see `.claude/agents/developer.md`'s Operating Context) and may honestly self-report `coverage_gate: SKIPPED(no-delegation)`; that is expected in this path, not a red flag. Record the result of _planner's own_ `qa-engineer` invocation and verify it is `PASS`, `FAIL`, or `SKIPPED(<reason>)` carrying a non-empty reason. An omitted result 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.
|
|
461
|
+
6. **Invoke `verifier` in Audit Mode directly** — scoped to this story's diff/branch/PR — immediately after step 5, and post its human-readable summary to the story PR via `github-ops` comment conventions. A bare developer-reported `verifier_audit: run` string is one signal but is **NOT sufficient evidence on its own** — `verifier_audit: not-run(no-delegation)` is a valid, expected self-report from the `developer` subagent in this path (it structurally cannot invoke `verifier`), not a red flag. This merge gate checks the result of _planner's own_ `verifier` invocation, not the self-reported field. The audit's drift findings (`fidelity_verdict`/`highest_drift_impact`/`drift_findings`) **MUST NOT** block the merge.
|
|
412
462
|
7. For migration-bearing stories, verify explicit user confirmation was recorded before migration apply.
|
|
413
463
|
8. Verify branch is up to date with integration branch (update/rebase if required by policy). Use the `git-ops` skill for rebase and conflict resolution.
|
|
414
464
|
9. Detect merge conflicts before attempting merge. If conflicts are found, invoke the `git-ops` skill to resolve them.
|
|
415
465
|
10. **Review the PR** — planner **MUST** review the story PR (verify scope, files, test and quality-gate results) and approve it.
|
|
416
466
|
11. Merge PR into integration branch using one consistent strategy (default: `squash`).
|
|
417
467
|
12. Confirm integration branch is green after merge before moving to next story.
|
|
418
|
-
13. **
|
|
468
|
+
13. **Verify the merge actually happened, then write checkpoint.** Before writing `✅ Merged` to the state file, confirm observed GitHub state — run `gh pr view <n> --json state,mergedAt` and require `state` to be `MERGED` and `mergedAt` to be non-null. If the check fails or errors, do **not** write `✅ Merged`; mark the story blocked, report the exact `gh pr view` output, and stop rather than guessing at the outcome. Only once this is confirmed: update the planner state file (see Phase 0.5 State File Format), mark the completed story as `✅ Merged` with its PR link and branch name, update `Current Position` to the next pending story, update the `Last updated` timestamp, and post a GitHub Issue comment on the plan/milestone issue with the current story status table.
|
|
419
469
|
|
|
420
470
|
If any merge gate fails, stop and report exact blocker and PR link.
|
|
421
471
|
|
|
@@ -442,13 +492,18 @@ After all stories are merged into integration:
|
|
|
442
492
|
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.
|
|
443
493
|
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.
|
|
444
494
|
4. Invoke `technical-writer` for a planner-level drift/stale-doc validation pass against integrated changes; unresolved drift **MUST** block handoff.
|
|
445
|
-
5.
|
|
446
|
-
6. **
|
|
447
|
-
7.
|
|
448
|
-
8.
|
|
449
|
-
|
|
450
|
-
|
|
451
|
-
|
|
495
|
+
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.
|
|
496
|
+
6. **memo run outcome.** Write the per-run outcome entry described in **memo-cli Integration → Responsibilities** and record `memo_run_outcome`.
|
|
497
|
+
7. Open one consolidated PR from integration branch to `main`.
|
|
498
|
+
8. **Do NOT merge.** Notify the user that the consolidated PR is ready for their review.
|
|
499
|
+
9. Wait for the user to approve and merge the PR into `main`.
|
|
500
|
+
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.
|
|
501
|
+
11. Before final handoff, **MUST** ensure the local working branch is the integration branch used for this run:
|
|
502
|
+
|
|
503
|
+
- Preferred: run `git checkout integration/<plan-id>-<short-description>`.
|
|
504
|
+
- 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.
|
|
505
|
+
|
|
506
|
+
12. Final user response **MUST** include a `PR Directives (User Action Required)` section with:
|
|
452
507
|
|
|
453
508
|
- consolidated PR URL
|
|
454
509
|
- current CI/check status
|
|
@@ -462,6 +517,8 @@ Consolidated PR should include:
|
|
|
462
517
|
- Per-story changed files and test results
|
|
463
518
|
- Manual validation instructions per story
|
|
464
519
|
- Integration test summary
|
|
520
|
+
- Roadmap row(s) updated in `docs/roadmap.md` (before → after status)
|
|
521
|
+
- Memo coverage: per-story `memo_intent` / `memo_outcome` values and `memo_run_outcome`
|
|
465
522
|
|
|
466
523
|
PR title **MUST** follow Conventional Commits and PR body **MUST** follow `github-ops` conventions.
|
|
467
524
|
|
|
@@ -469,22 +526,34 @@ Planner **MUST NOT** merge the consolidated PR. Only the user may approve and me
|
|
|
469
526
|
|
|
470
527
|
---
|
|
471
528
|
|
|
529
|
+
## Roadmap Maintenance
|
|
530
|
+
|
|
531
|
+
`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.
|
|
532
|
+
|
|
533
|
+
- **Read** it in Phase 0 (see **Roadmap Read**).
|
|
534
|
+
- **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.
|
|
535
|
+
- Change only the rows this run touched; rows for other PRDs belong to `product-engineer` and to the planner runs that deliver them.
|
|
536
|
+
- The `verifier` rollup audit (Phase 5 step 3) compares the roadmap against merged work and reports a mismatch as an advisory finding.
|
|
537
|
+
|
|
538
|
+
---
|
|
539
|
+
|
|
472
540
|
## Error Handling
|
|
473
541
|
|
|
474
|
-
| Situation | Action
|
|
475
|
-
| ---------------------------------- |
|
|
476
|
-
| No `/workstream` task file | Ask for file path or milestone
|
|
477
|
-
| Multiple task files | Ask user to choose
|
|
478
|
-
| Milestone has no issues | Report and stop
|
|
479
|
-
| Circular dependencies | Report cycle and stop
|
|
480
|
-
| Story returns blocked | Mark blocked and ask whether to continue
|
|
481
|
-
| Story PR targets wrong base | Require retargeting to integration branch before merge
|
|
482
|
-
| Required checks pending/failing | Do not merge; report failing checks
|
|
483
|
-
| Story PR behind integration branch | Require update/rebase before merge
|
|
484
|
-
| Merge conflict | Invoke `git-ops` skill to resolve; if resolution fails, report conflicting files and pause
|
|
485
|
-
| Integration tests fail | Report failures and ask whether to proceed or fix first
|
|
486
|
-
| Consolidated PR creation fails | Return generated title/body and ask to retry
|
|
487
|
-
| Story payload base mismatch | Mark story blocked; require retargeting PR base to integration branch before merge
|
|
542
|
+
| Situation | Action |
|
|
543
|
+
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
|
544
|
+
| No `/workstream` task file | Ask for file path or milestone |
|
|
545
|
+
| Multiple task files | Ask user to choose |
|
|
546
|
+
| Milestone has no issues | Report and stop |
|
|
547
|
+
| Circular dependencies | Report cycle and stop |
|
|
548
|
+
| Story returns blocked | Mark blocked and ask whether to continue |
|
|
549
|
+
| Story PR targets wrong base | Require retargeting to integration branch before merge |
|
|
550
|
+
| Required checks pending/failing | Do not merge; report failing checks |
|
|
551
|
+
| Story PR behind integration branch | Require update/rebase before merge |
|
|
552
|
+
| Merge conflict | Invoke `git-ops` skill to resolve; if resolution fails, report conflicting files and pause |
|
|
553
|
+
| Integration tests fail | Report failures and ask whether to proceed or fix first |
|
|
554
|
+
| Consolidated PR creation fails | Return generated title/body and ask to retry |
|
|
555
|
+
| Story payload base mismatch | Mark story blocked; require retargeting PR base to integration branch before merge |
|
|
556
|
+
| Merge command blocked by git-guard | Report the block message verbatim; mark the story blocked; write the checkpoint; ask the user. Never attempt an alternative merge command, tool surface, or sequence to achieve the same effect — a blocked guard is a decision, not an obstacle |
|
|
488
557
|
|
|
489
558
|
---
|
|
490
559
|
|
|
@@ -504,7 +573,7 @@ Planner **MUST NOT** merge the consolidated PR. Only the user may approve and me
|
|
|
504
573
|
- All GitHub outputs are in English.
|
|
505
574
|
- Final user-facing local branch state **MUST** be the integration branch for the current run, or planner **MUST** explicitly report verification failure and provide the exact checkout command.
|
|
506
575
|
- Planner **MUST** end a successful run with explicit PR directives for the user (review/approve/merge) and **MUST NOT** mark the run complete before that handoff is emitted.
|
|
507
|
-
- Planner **MUST**
|
|
576
|
+
- Planner **MUST** invoke `qa-engineer` and `verifier` (Audit Mode) directly, scoped to each story's diff/branch/PR, before merging that story's PR into the integration branch (merge gates 5 and 6) — a story's self-reported `coverage_gate`/`verifier_audit` fields are supporting context only, never sufficient evidence on their own, and `not-run(no-delegation)`/`SKIPPED(no-delegation)` are valid, expected self-reports from the `developer` subagent, not red flags. Planner **MUST** also invoke `verifier` in `audit` mode for a PRD-level rollup audit before/alongside the consolidated PR. All these triggers are mandatory and non-skippable, and none of their drift findings block the corresponding merge/handoff.
|
|
508
577
|
|
|
509
578
|
---
|
|
510
579
|
|
|
@@ -71,8 +71,39 @@ If any required input is missing, you **MUST** ask concise clarifying questions.
|
|
|
71
71
|
|
|
72
72
|
---
|
|
73
73
|
|
|
74
|
+
## Roadmap Maintenance
|
|
75
|
+
|
|
76
|
+
`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.
|
|
77
|
+
|
|
78
|
+
- **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.
|
|
79
|
+
- **Create it** in Init Mode, or the first time a PRD is written in a repository that has none, from the template shape below.
|
|
80
|
+
- **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.
|
|
81
|
+
- **Fill `Issues/PRs` when stories are published** (`activity-publish-github`), and set the row to `In progress` once its first story is being implemented.
|
|
82
|
+
- **Correct it during drift reconciliation** (`activity-drift-reconciliation`) when a `verifier` roadmap-mismatch finding is confirmed.
|
|
83
|
+
- 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.
|
|
84
|
+
|
|
85
|
+
Shape (one table, one row per PRD phase or wave, newest PRD first):
|
|
86
|
+
|
|
87
|
+
```markdown
|
|
88
|
+
# Roadmap
|
|
89
|
+
|
|
90
|
+
Last updated: YYYY-MM-DD
|
|
91
|
+
|
|
92
|
+
| PRD | Phase/Wave | Scope (one line) | Status | Issues/PRs | What's missing |
|
|
93
|
+
| ---------------------------------------- | ---------- | ---------------- | ----------- | ----------- | ---------------- |
|
|
94
|
+
| [prd-<name>](requirements/prd-<name>.md) | 1 | <scope> | Not started | #12, PR #20 | <remaining or —> |
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
`Status` is exactly one of `Not started`, `In progress`, `Done`.
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
74
101
|
## memo-cli Integration (When Available)
|
|
75
102
|
|
|
103
|
+
### Bank Declaration
|
|
104
|
+
|
|
105
|
+
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).
|
|
106
|
+
|
|
76
107
|
### Availability Check
|
|
77
108
|
|
|
78
109
|
At the start of every session, verify memo-cli is configured:
|
|
@@ -81,7 +112,8 @@ At the start of every session, verify memo-cli is configured:
|
|
|
81
112
|
which memo && memo setup validate
|
|
82
113
|
```
|
|
83
114
|
|
|
84
|
-
- If `memo` is not found, skip all memo operations
|
|
115
|
+
- If `memo` is not found and `memo.config.json` does not exist, skip all memo operations.
|
|
116
|
+
- 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.
|
|
85
117
|
- 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."
|
|
86
118
|
|
|
87
119
|
### Session Start — Restore Context
|
|
@@ -116,7 +148,35 @@ Before making design choices in `activity-refine`, `activity-generate-spec`, or
|
|
|
116
148
|
memo search "<specific topic, technology, or module>" --json
|
|
117
149
|
```
|
|
118
150
|
|
|
119
|
-
|
|
151
|
+
### Decision Write-Back — After Each Grilling Exit Gate
|
|
152
|
+
|
|
153
|
+
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`.
|
|
154
|
+
|
|
155
|
+
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.
|
|
156
|
+
|
|
157
|
+
```bash
|
|
158
|
+
memo write \
|
|
159
|
+
--kind semantic \
|
|
160
|
+
--bank kb \
|
|
161
|
+
--manual \
|
|
162
|
+
--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>." \
|
|
163
|
+
--tags "<domain>,<feature>,decision,<phase-lowercase>,<feature>-d-NN" \
|
|
164
|
+
--entry-type decision \
|
|
165
|
+
--story "<issue-or-feature-id-if-known>" \
|
|
166
|
+
--files "workstream/decisions-<feature>.md" \
|
|
167
|
+
--on-duplicate consolidate \
|
|
168
|
+
--json
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
- `--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.
|
|
172
|
+
- 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.
|
|
173
|
+
- **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.
|
|
174
|
+
|
|
175
|
+
`technical-writer` still owns ADR and doc-change entries, and `developer` owns per-story intent/outcome entries.
|
|
176
|
+
|
|
177
|
+
### Session Close
|
|
178
|
+
|
|
179
|
+
No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4.0.
|
|
120
180
|
|
|
121
181
|
---
|
|
122
182
|
|
|
@@ -147,9 +207,8 @@ This agent invokes the following **skills** for each activity. You **MUST** load
|
|
|
147
207
|
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."
|
|
148
208
|
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.
|
|
149
209
|
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).
|
|
150
|
-
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.
|
|
151
|
-
10. **
|
|
152
|
-
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.
|
|
210
|
+
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.
|
|
211
|
+
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.
|
|
153
212
|
|
|
154
213
|
---
|
|
155
214
|
|
|
@@ -159,13 +218,12 @@ This agent invokes the following **skills** for each activity. You **MUST** load
|
|
|
159
218
|
|
|
160
219
|
Follow the `activity-init` skill:
|
|
161
220
|
|
|
162
|
-
1. **Detect repository mode
|
|
221
|
+
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.
|
|
163
222
|
2. **Route by mode:**
|
|
164
|
-
- **
|
|
165
|
-
- **
|
|
166
|
-
- **Undocumented/greenfield:** Run `dt extract detect` → `dt extract all --interactive` → present extraction report → then conduct the interview.
|
|
223
|
+
- **Documented repository:** Proceed with the standard interview (current flow unchanged).
|
|
224
|
+
- **Undocumented/greenfield:** Investigate the codebase directly (manifest files, directory structure, README) → present a findings summary → then conduct the interview.
|
|
167
225
|
3. Ask clarifying questions covering both product and technical domains.
|
|
168
|
-
4. Generate `product
|
|
226
|
+
4. Generate `product.md` and `tech.md` in `/docs/`, including the package map.
|
|
169
227
|
5. If `/DESIGN.md` is missing and the project has UI scope, create a baseline `/DESIGN.md` aligned with current product direction.
|
|
170
228
|
6. Present generated documents for user review.
|
|
171
229
|
7. Iterate based on feedback.
|
|
@@ -179,7 +237,7 @@ Follow the `activity-refine` skill (PRD mode):
|
|
|
179
237
|
|
|
180
238
|
1. Gather feature scope from user.
|
|
181
239
|
2. Ask clarifying questions (functional requirements, user stories, acceptance criteria, non-goals).
|
|
182
|
-
3. Reference `product
|
|
240
|
+
3. Reference `product.md` and `tech.md`.
|
|
183
241
|
4. Produce PRD: `/docs/requirements/prd-[feature-name].md`
|
|
184
242
|
5. Present for user review and iterate.
|
|
185
243
|
|
|
@@ -10,11 +10,10 @@ Delegate to the **`researcher` subagent** (via the Task tool) for a codebase inv
|
|
|
10
10
|
The subagent runs one procedure:
|
|
11
11
|
|
|
12
12
|
1. **Intake** — receives the research question; asks one clarification if vague.
|
|
13
|
-
2. **
|
|
14
|
-
3. **
|
|
15
|
-
4. **
|
|
16
|
-
5. **
|
|
17
|
-
6. **Provenance** — records repository, branch, commit SHA, date; consumers treat the artifact as stale when HEAD advances.
|
|
13
|
+
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.
|
|
14
|
+
3. **Synthesis** — writes answer-first summary, compiles relevance-ranked file map, derives relationships, risks, and gaps.
|
|
15
|
+
4. **Budget enforcement** — ensures report <= 250 lines and <= 30 cited files.
|
|
16
|
+
5. **Provenance** — records repository, branch, commit SHA, date; consumers treat the artifact as stale when HEAD advances.
|
|
18
17
|
|
|
19
18
|
The subagent will **not**:
|
|
20
19
|
|
|
@@ -7,4 +7,4 @@ Delegate to the **`technical-writer` subagent** (via the Task tool) to update do
|
|
|
7
7
|
|
|
8
8
|
**Context:** $ARGUMENTS
|
|
9
9
|
|
|
10
|
-
The subagent updates `/docs` artifacts, creates a new ADR in `/docs/adr/` if `
|
|
10
|
+
The subagent updates `/docs` artifacts, creates a new ADR in `/docs/adr/` if `tech.md` changed, updates `/docs/user-guide/` for user-visible changes, and keeps docs-site navigation in sync with pages on disk. It never modifies application code.
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
#!/usr/bin/env bash
|
|
2
|
+
# dev-tasks PreToolUse guard for write tools (Edit, Write, NotebookEdit).
|
|
3
|
+
#
|
|
4
|
+
# Blocks file writes when the current branch is the default branch (`main`).
|
|
5
|
+
# This is a best-effort safety net — the primary enforcement is the agent
|
|
6
|
+
# prompt's branch gate language. This hook catches cases where the prompt
|
|
7
|
+
# gate was bypassed or ignored.
|
|
8
|
+
#
|
|
9
|
+
# Contract: receives the PreToolUse hook payload as JSON on stdin. Exit code 2
|
|
10
|
+
# blocks the tool call; exit 0 allows. Any unexpected error exits 0 (fail-open)
|
|
11
|
+
# so the guard never wedges a session.
|
|
12
|
+
|
|
13
|
+
set -uo pipefail
|
|
14
|
+
|
|
15
|
+
# Determine the current branch. If git is unavailable or we're not in a repo,
|
|
16
|
+
# fail open (allow the write).
|
|
17
|
+
current_branch="$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo '')"
|
|
18
|
+
|
|
19
|
+
if [ -z "$current_branch" ]; then
|
|
20
|
+
# Not in a git repo or git unavailable — fail open.
|
|
21
|
+
exit 0
|
|
22
|
+
fi
|
|
23
|
+
|
|
24
|
+
if [ "$current_branch" = "main" ]; then
|
|
25
|
+
printf 'BLOCKED by dev-tasks branch-guard: write operation attempted while on the default branch (main). You MUST create a feature branch (issue/* or story/*) before writing implementation code.\n' >&2
|
|
26
|
+
exit 2
|
|
27
|
+
fi
|
|
28
|
+
|
|
29
|
+
# On a feature branch — allow the write.
|
|
30
|
+
exit 0
|