@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
|
@@ -33,26 +33,72 @@ This activity assumes:
|
|
|
33
33
|
|
|
34
34
|
---
|
|
35
35
|
|
|
36
|
+
## Package Scope in Commits
|
|
37
|
+
|
|
38
|
+
In a monorepo the package is the Conventional Commits **scope** (FR-63):
|
|
39
|
+
|
|
40
|
+
```
|
|
41
|
+
feat(api): add token-refresh endpoint
|
|
42
|
+
fix(web): stop double-submitting the checkout form
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
- Take the scope from the package map in `docs/tech.md`. Use the short,
|
|
46
|
+
readable form of the package name, not the full specifier: `@acme/api`
|
|
47
|
+
becomes `api`.
|
|
48
|
+
- A package name that is not a valid scope — one containing a space, a
|
|
49
|
+
slash after stripping the org prefix, or an uppercase letter — is
|
|
50
|
+
reduced to a lowercase, hyphenated form and the mapping is recorded in
|
|
51
|
+
the package map's row so every commit uses the same one. Never invent
|
|
52
|
+
a different short form per commit.
|
|
53
|
+
- A commit spanning packages uses the broadest honest scope, or none. A
|
|
54
|
+
scope that names one package for a change touching four is worse than
|
|
55
|
+
no scope.
|
|
56
|
+
- In a **single-package repository the scope is optional**. Omit it —
|
|
57
|
+
`feat: add the endpoint` — rather than writing an empty scope `feat():`,
|
|
58
|
+
which is not valid Conventional Commits and which the commit hook
|
|
59
|
+
rejects.
|
|
60
|
+
|
|
61
|
+
## Platform-Write Routing
|
|
62
|
+
|
|
63
|
+
- You **MUST NOT** emit or execute a platform write command (`aws`, `flyctl`, `supabase`, or Cloudflare API writes) while executing a task list.
|
|
64
|
+
- When a sub-task's work is a platform write, you **MUST** route it to `infra-engineer` instead of running it yourself, so the approval, revert, and backup gates bind. The sub-task kinds that route are: **secrets**, **deploy**, **DNS**, **certificates**, **IAM policy**, and **migrations against a shared or cloud project**.
|
|
65
|
+
- This routing is **conditional**, never mandatory: a story with no platform-write scope invokes nothing, and an infra-shaped but local-only sub-task — such as editing `.env.example` or a config template checked into the repo — stays with the implementing agent.
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
36
69
|
## Before Starting Work
|
|
37
70
|
|
|
38
71
|
1. You **MUST** confirm the GitHub Issue is open.
|
|
39
|
-
2. **
|
|
72
|
+
2. **Decision-log read (non-mutating — runs before any branch is created):** You **MUST** read `workstream/decisions-<feature>.md` in full, alongside (not replacing) the GitHub-issue-open check in step 1 — both checks run before branch creation. This step is ordered before the branch gate (step 3) precisely because it is non-mutating: reading it first lets you answer your own procedural questions (e.g., "was this file's location already decided?") from the log before touching git. If `workstream/decisions-<feature>.md` does not exist — for example, a pre-Phase-2 feature, or a feature for which grilling never ran — you **MUST** proceed without the read, noting its absence in your status output, rather than failing or blocking. This is an enrichment, never a hard gate: a missing decision log never blocks starting work. A decision log that exists but has zero rows is treated the same as present-and-populated — there is simply nothing to cite.
|
|
73
|
+
3. **Branch gate (hard requirement):** You **MUST** verify you are on a feature branch before any implementation work:
|
|
40
74
|
- Run `git rev-parse --abbrev-ref HEAD` to determine the current branch.
|
|
41
75
|
- If HEAD is the default branch (`main`) or does not match `issue/*` or `story/*` pattern, you **MUST** create a new branch from the latest default branch by delegating branch naming and creation to `github-ops` whenever possible.
|
|
42
76
|
- You **MUST NOT** proceed with any implementation sub-task, write any code, create any files, or make any commits until a feature branch is checked out.
|
|
43
|
-
- If HEAD is already a valid feature branch (matching `issue/*` or `story/*`), proceed to step
|
|
77
|
+
- If HEAD is already a valid feature branch (matching `issue/*` or `story/*`), proceed to step 4.
|
|
44
78
|
- Branch format: `issue/<issue-number>-<short-description>` or `story/<id>-<short-description>`
|
|
45
|
-
|
|
79
|
+
4. You **MUST** open a **draft Pull Request** by delegating to `github-ops` whenever possible.
|
|
46
80
|
- A PR requires at least one commit. Open it immediately after the first commit on the feature branch — never before — and you **MUST NOT** continue past that first commit without it.
|
|
47
81
|
- Base branch is the default branch unless an orchestrating caller explicitly provides a base-branch override.
|
|
48
82
|
- PR title **MUST** follow Conventional Commits (e.g., `feat: implement issue 37`).
|
|
49
83
|
- PR description **MUST** include `Closes #<issue-number>`.
|
|
50
|
-
|
|
84
|
+
5. You **MUST** ensure the task list in the GitHub Issue matches the local `/workstream/tasks-*.md` file.
|
|
85
|
+
6. **memo intent (when memo-cli is available):** Before the first implementation sub-task, you **MUST** run the memo-cli Availability Check and write the episodic intent entry defined in the `developer` agent contract (**memo-cli Integration → Intent Entry**), naming the bank literally (`--bank developer-memory`, never `--bank $MEMO_BANK`). Record `memo_intent` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — a failed write is retried once and then reported, never dropped silently.
|
|
51
86
|
|
|
52
87
|
If `github-ops` delegation is unavailable in the current runtime, you **MUST** apply `github-ops` conventions directly and explicitly note that fallback in your status output.
|
|
53
88
|
|
|
54
89
|
---
|
|
55
90
|
|
|
91
|
+
## Decision-Log Citation
|
|
92
|
+
|
|
93
|
+
When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
94
|
+
|
|
95
|
+
- An implementation commit whose approach was shaped by a decision **MUST** cite it in the commit body — e.g. a trailing line `Follows D-NN: <short form>.` — using the feature's own unqualified `D-NN` form (the file belongs to one feature; the qualified `<feature>#D-NN` cross-file form is `activity-grill`/`activity-refine`/`activity-generate-spec`'s concern, not `implement`'s).
|
|
96
|
+
- The PR body **MUST** reference every consumed decision ID it draws on, in its Completion Report area, alongside the existing `Closes #<issue-number>` line.
|
|
97
|
+
- This is **additive only**, mirroring `plan`'s own citation contract: a commit or PR with no traceable decision cites none. You **MUST NOT** fabricate a citation to give a commit or PR one.
|
|
98
|
+
- When step 2 found no `workstream/decisions-<feature>.md` (absent or empty), there is nothing to cite — omit the citation, do not fabricate one, and do not treat the omission as a defect.
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
56
102
|
## During Implementation
|
|
57
103
|
|
|
58
104
|
### Step-by-Step Execution
|
|
@@ -103,14 +149,17 @@ If `github-ops` delegation is unavailable in the current runtime, you **MUST** a
|
|
|
103
149
|
5. `technical-writer` validation **MUST** include a drift/stale-doc check report, and completion **MUST NOT** proceed while unresolved drift remains.
|
|
104
150
|
6. A `qa-engineer` pass **MUST** have run and `coverage_gate` **MUST** be recorded as `PASS`, `FAIL`, or `SKIPPED(<reason>)`. The reason **MUST** be non-empty when skipped; an omitted field is treated as incomplete. A `FAIL` or `SKIPPED` value does not block completion — only omission does.
|
|
105
151
|
7. A `verifier` audit in `audit` mode **MUST** have run against the delivered implementation, with its human-readable summary posted to the issue/PR. This gate is mandatory and non-skippable — it **MUST NOT** be skipped regardless of drift findings, and drift findings reported by this audit **MUST NOT** block completion. This condition is satisfied once the audit has run and been posted; any resulting drift is handled by `product-engineer`'s `activity-drift-reconciliation` flow after this gate, not before it.
|
|
106
|
-
8.
|
|
107
|
-
9. The PR **MUST** be
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
152
|
+
8. **memo outcome (when memo-cli is available):** Before the PR is converted to ready for review, you **MUST** write the episodic outcome entry defined in the `developer` agent contract (**memo-cli Integration → Outcome Entry**) and record `memo_outcome` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`. A `failed` or `skipped` value does not block completion — only an omitted field does.
|
|
153
|
+
9. The PR **MUST** be converted from draft to ready for review.
|
|
154
|
+
10. The PR **MUST** be approved by the appropriate reviewer per the merge authority policy in `github-ops`:
|
|
155
|
+
|
|
156
|
+
- PRs targeting an **integration branch**: `planner` reviews and approves.
|
|
157
|
+
- PRs targeting **`main`**: the **user** reviews and approves.
|
|
158
|
+
|
|
159
|
+
11. The PR **MUST** be merged by the authorized party (planner for integration branches, user for `main`).
|
|
160
|
+
12. You **MUST NOT** close the GitHub Issue until the PR is approved **AND** merged.
|
|
161
|
+
13. You **MUST NOT** close the issue while the PR is still in draft or pending review.
|
|
162
|
+
14. You **MUST** notify the user when the PR is ready for review — explicitly inform them so they can review and merge.
|
|
114
163
|
|
|
115
164
|
---
|
|
116
165
|
|
package/.kiro/steering/plan.md
CHANGED
|
@@ -65,7 +65,7 @@ The task list **MUST** follow this structure:
|
|
|
65
65
|
|
|
66
66
|
- [ ] 1.0 Implement Story [ID]: [Story Title] (or: Implement Issue [#] - [Github_Issue_URL]: [Title])
|
|
67
67
|
|
|
68
|
-
- [ ] 1.1 [First implementation step]
|
|
68
|
+
- [ ] 1.1 [First implementation step] (D-NN, when traceable — omit otherwise)
|
|
69
69
|
- [ ] 1.2 [Second implementation step]
|
|
70
70
|
- [ ] 1.x Verify Acceptance Criterion: [Criterion 1]
|
|
71
71
|
- [ ] 1.y Verify Acceptance Criterion: [Criterion 2]
|
|
@@ -74,8 +74,48 @@ The task list **MUST** follow this structure:
|
|
|
74
74
|
- [ ] 2.0 Implement Story [ID]: [Story Title] (or: Implement Issue [#] - [Github_Issue_URL]: [Title])
|
|
75
75
|
- [ ] 2.1 [First implementation step]
|
|
76
76
|
- ...
|
|
77
|
+
|
|
78
|
+
## Decisions Consumed
|
|
79
|
+
|
|
80
|
+
| ID | Decision (short form) |
|
|
81
|
+
| ---- | --------------------- |
|
|
82
|
+
| D-NN | … |
|
|
77
83
|
```
|
|
78
84
|
|
|
85
|
+
## Decision Citations
|
|
86
|
+
|
|
87
|
+
A task line that derives from a specific decision cites it inline, at the
|
|
88
|
+
end of the line: `- [ ] 3.2 Add cap-reached prompt (D-55)` (FR-16).
|
|
89
|
+
|
|
90
|
+
- Citations reference the feature's own `decisions-<feature>.md` by
|
|
91
|
+
unqualified `D-NN` — a task list belongs to exactly one feature, so the
|
|
92
|
+
qualified `<feature>#D-NN` form `activity-refine`/`activity-generate-spec`
|
|
93
|
+
use for cross-feature reuse is never needed here.
|
|
94
|
+
- This is **additive only**: a task with no traceable decision cites none.
|
|
95
|
+
You **MUST NOT** fabricate a citation to give a task one.
|
|
96
|
+
- The task list closes with a `## Decisions Consumed` section aggregating
|
|
97
|
+
every decision ID cited anywhere in the list, in the same `ID | Decision
|
|
98
|
+
(short form)` table shape the decision log itself uses. A task list that
|
|
99
|
+
cites no decisions still includes the section, empty (header plus
|
|
100
|
+
table skeleton, no rows) — consistent with how `activity-refine`'s and
|
|
101
|
+
`activity-generate-spec`'s own `## Decisions` sections may legitimately
|
|
102
|
+
be empty.
|
|
103
|
+
|
|
104
|
+
## Package Attribution
|
|
105
|
+
|
|
106
|
+
Every task **MUST** name the package it changes (FR-63), so a reader can
|
|
107
|
+
tell the blast radius from the task list without opening the diff.
|
|
108
|
+
|
|
109
|
+
- Read the package map in `docs/tech.md` for the package list.
|
|
110
|
+
- Write the package in the sub-task text, in brackets, first:
|
|
111
|
+
`- [ ] 1.1 [@acme/api] Add the token-refresh endpoint`.
|
|
112
|
+
- A sub-task touching several packages lists them all. A sub-task that
|
|
113
|
+
touches _most_ packages is usually the wrong size — split it.
|
|
114
|
+
- In a **single-package repository the bracket is omitted**, not left
|
|
115
|
+
empty. It is optional there, never blank.
|
|
116
|
+
- Non-code tasks (docs, workflow files) that belong to no package use
|
|
117
|
+
`[repo root]`.
|
|
118
|
+
|
|
79
119
|
## Conversion Guidelines
|
|
80
120
|
|
|
81
121
|
When converting a **User Story** or **Refined Issue** to a **Parent Task**:
|
|
@@ -94,6 +134,7 @@ When converting a **User Story** or **Refined Issue** to a **Parent Task**:
|
|
|
94
134
|
- If schema or data-model changes are involved, migration tasks are **required by default**; omission is allowed only with an explicit documented opt-out rationale.
|
|
95
135
|
- Migration flows **MUST** include: create migration artifact, document rollback/impact, request user confirmation before apply, apply migration after confirmation, and verify applied state.
|
|
96
136
|
- If the story involves data models, you **SHOULD** include a sub-task to generate seed data.
|
|
137
|
+
- When `workstream/decisions-<feature>.md` exists, you **MUST** cite the decision ID inline (`… (D-NN)`) on any sub-task whose approach or scope traces to a specific decision row, and **MUST** populate the closing `## Decisions Consumed` section with every ID cited anywhere in the list. This is additive only — a sub-task with no traceable decision cites none; do not fabricate a citation.
|
|
97
138
|
|
|
98
139
|
3. **Context:** You **MAY** add a `> Note:` block under the parent task for quick reference (User Story text or Business Rules), but the checkbox structure **MUST** remain clean.
|
|
99
140
|
4. **Relevant Files:** You **MUST** aggregate all "Files to Create/Modify" from selected stories into the top-level `Relevant Files` section.
|
|
@@ -139,6 +180,7 @@ If this is a **greenfield project** or a **new component**, you **MUST** include
|
|
|
139
180
|
5. You **MUST** ensure all Implementation Steps, Acceptance Criteria, and Testing requirements are preserved as sub-tasks.
|
|
140
181
|
6. For JS/TS repositories, you **MUST** prefer `pnpm` commands and canonical script names in generated tasks.
|
|
141
182
|
7. You **MUST** ensure each task includes both implementation and test/validation steps, including edge-case validation.
|
|
183
|
+
7a. When a decision log exists for the feature, you **MUST** cite the decision ID inline on any traceable sub-task and populate the closing `## Decisions Consumed` section (FR-16) — additively, never fabricated.
|
|
142
184
|
8. For schema/data-model changes, you **MUST** include migration lifecycle tasks and an explicit user-confirmation gate before applying migrations unless an opt-out rationale is documented.
|
|
143
185
|
9. You **MUST** update the corresponding GitHub Issue(s) with the task checklist by delegating to `github-ops` whenever possible. If no issue exists, you **MUST** ask the user whether to create one first.
|
|
144
186
|
10. You **MUST** save the task list file.
|
package/AGENTS.md
CHANGED
|
@@ -4,10 +4,11 @@ Portable, repo-installed workflow harness for structured, PRD-driven AI-assisted
|
|
|
4
4
|
|
|
5
5
|
## Contracts
|
|
6
6
|
|
|
7
|
-
| File
|
|
8
|
-
|
|
|
9
|
-
| `/DESIGN.md`
|
|
10
|
-
| `/TESTING.md`
|
|
7
|
+
| File | Owner | Purpose |
|
|
8
|
+
| ----------------- | ------------------ | ---------------------------------------------- |
|
|
9
|
+
| `/DESIGN.md` | `ux-engineer` | Canonical design-system tokens and UI guidance |
|
|
10
|
+
| `/TESTING.md` | `qa-engineer` | Layer taxonomy, runners, thresholds, fixtures |
|
|
11
|
+
| `docs/roadmap.md` | `product-engineer` | PRD phases/waves: done, in progress, missing |
|
|
11
12
|
|
|
12
13
|
If `/DESIGN.md` is missing and scope includes UI work, agents **MUST** create a baseline before finalizing design-dependent outputs. An unfilled `/TESTING.md` placeholder means "no standard established", never permission.
|
|
13
14
|
|
|
@@ -21,53 +22,58 @@ If `/DESIGN.md` is missing and scope includes UI work, agents **MUST** create a
|
|
|
21
22
|
|
|
22
23
|
## Agents
|
|
23
24
|
|
|
24
|
-
| Agent | Purpose
|
|
25
|
-
| -------------------- |
|
|
26
|
-
| **product-engineer** | Preparation — PRD, spec, stories, plan. Owns drift-reconciliation.
|
|
27
|
-
| **developer** | Execution — implements from task lists with mandatory verifier audit pre-PR.
|
|
28
|
-
| **planner** | Multi-story orchestration with dependency ordering and integration PR.
|
|
29
|
-
| **technical-writer** | Autonomous documentation maintenance.
|
|
30
|
-
| **housekeeping** | Lint, type, and test-wiring fixes.
|
|
31
|
-
| **github-ops** | GitHub consistency — issues, PRs, branches, labels, milestones, merge authority.
|
|
32
|
-
| **ux-engineer** | UX prototyping, DESIGN.md ownership, mockup generation.
|
|
33
|
-
| **qa-engineer** | Testing standard, test authoring, coverage/gap reporting.
|
|
34
|
-
| **researcher** | Bounded codebase investigation producing structured research artifacts.
|
|
35
|
-
| **verifier** | Compliance test-plan design and post-implementation fidelity audit.
|
|
36
|
-
|
|
37
|
-
|
|
25
|
+
| Agent | Purpose |
|
|
26
|
+
| -------------------- | --------------------------------------------------------------------------------------------------------- |
|
|
27
|
+
| **product-engineer** | Preparation — PRD, spec, stories, plan. Owns drift-reconciliation. |
|
|
28
|
+
| **developer** | Execution — implements from task lists with mandatory verifier audit pre-PR. |
|
|
29
|
+
| **planner** | Multi-story orchestration with dependency ordering and integration PR. |
|
|
30
|
+
| **technical-writer** | Autonomous documentation maintenance. **Owns docs structure and content**, including `docs/runbooks/`. |
|
|
31
|
+
| **housekeeping** | Lint, type, and test-wiring fixes. Does **not** organize documentation. |
|
|
32
|
+
| **github-ops** | GitHub consistency — issues, PRs, branches, labels, milestones, merge authority. |
|
|
33
|
+
| **ux-engineer** | UX prototyping, DESIGN.md ownership, mockup generation. |
|
|
34
|
+
| **qa-engineer** | Testing standard, test authoring, coverage/gap reporting. |
|
|
35
|
+
| **researcher** | Bounded codebase investigation producing structured research artifacts. |
|
|
36
|
+
| **verifier** | Compliance test-plan design and post-implementation fidelity audit. |
|
|
37
|
+
| **infra-engineer** | Approval-gated, reversible, recorded infrastructure changes across AWS, fly.io, Supabase, and Cloudflare. |
|
|
38
|
+
|
|
39
|
+
Platform coverage: `.github/agents/` and `.kiro/agents/` carry all eleven. `.claude/agents/` carries eight — `planner`, `product-engineer`, and `infra-engineer` run as `.claude/commands/` (they need main-thread human-approval gates: per-step for `infra-engineer`, per-phase for the two orchestrators).
|
|
38
40
|
|
|
39
41
|
## Skills
|
|
40
42
|
|
|
41
43
|
### Activity Skills
|
|
42
44
|
|
|
43
|
-
| Skill | Purpose
|
|
44
|
-
| ---------------------------------------- |
|
|
45
|
-
| activity-init | Establish product context and technical guidelines
|
|
46
|
-
| activity-refine | Issue refinement or full PRD creation
|
|
47
|
-
| activity-
|
|
48
|
-
| activity-
|
|
49
|
-
| activity-generate-
|
|
50
|
-
| activity-
|
|
51
|
-
| activity-
|
|
52
|
-
| activity-
|
|
53
|
-
| activity-
|
|
54
|
-
| activity-
|
|
55
|
-
| activity-test-
|
|
56
|
-
| activity-test-
|
|
57
|
-
| activity-
|
|
58
|
-
| activity-
|
|
59
|
-
| activity-
|
|
60
|
-
| activity-coverage-gap-analysis | Coverage measurement or structural gap analysis
|
|
61
|
-
| activity-drift-reconciliation | Route drift findings to task expansion or spec write-back
|
|
45
|
+
| Skill | Purpose | Consumer |
|
|
46
|
+
| ---------------------------------------- | ------------------------------------------------------------------------------------------- | ---------------- |
|
|
47
|
+
| activity-init | Establish product context and technical guidelines | product-engineer |
|
|
48
|
+
| activity-refine | Issue refinement or full PRD creation | product-engineer |
|
|
49
|
+
| activity-grill | One-question-at-a-time, depth-first interview to a confirmed shared-understanding exit gate | product-engineer |
|
|
50
|
+
| activity-codebase-research | Bounded codebase investigation with structured artifact | researcher |
|
|
51
|
+
| activity-generate-spec | PRD to technical specification | product-engineer |
|
|
52
|
+
| activity-generate-stories | Spec to user stories with coverage validation | product-engineer |
|
|
53
|
+
| activity-publish-github | Publish stories as GitHub Issues | product-engineer |
|
|
54
|
+
| activity-e2e-test-design | E2E scenario generation from spec/stories | verifier |
|
|
55
|
+
| activity-contract-test-design | Contract and schema compatibility test strategy | verifier |
|
|
56
|
+
| activity-edge-case-refinement | Systematic edge-case discovery | verifier |
|
|
57
|
+
| activity-random-test-tactics | Randomized/fuzz/property test generation | verifier |
|
|
58
|
+
| activity-test-standards | Establish/maintain TESTING.md, detect harness defects | qa-engineer |
|
|
59
|
+
| activity-test-implementation | Author Layer 1-2 tests with security-negative category | qa-engineer |
|
|
60
|
+
| activity-integration-test-implementation | Layer 2.5 tests against real databases | qa-engineer |
|
|
61
|
+
| activity-e2e-test-implementation | Playwright E2E from verifier scenario tables | qa-engineer |
|
|
62
|
+
| activity-coverage-gap-analysis | Coverage measurement or structural gap analysis | qa-engineer |
|
|
63
|
+
| activity-drift-reconciliation | Route drift findings to task expansion or spec write-back | product-engineer |
|
|
62
64
|
|
|
63
65
|
### Operational Skills
|
|
64
66
|
|
|
65
|
-
| Skill | Purpose
|
|
66
|
-
| -------------- |
|
|
67
|
-
| git-ops | Branch management, rebase, merge, conflict resolution
|
|
68
|
-
|
|
|
69
|
-
|
|
|
70
|
-
|
|
|
67
|
+
| Skill | Purpose | Consumer |
|
|
68
|
+
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
|
|
69
|
+
| git-ops | Branch management, rebase, merge, conflict resolution | developer, planner |
|
|
70
|
+
| aws-ops | AWS CLI command sets, tiers, cost, backup/revert, log table | infra-engineer |
|
|
71
|
+
| fly-ops | flyctl command sets, tiers, cost, backup/revert, log table | infra-engineer |
|
|
72
|
+
| supabase-ops | Supabase CLI command sets, `db diff` flow, drift rule, backup/revert, log table | infra-engineer |
|
|
73
|
+
| deploy-ops | Deploy script contract, environment mapping, tag policy, deploy-target framing, and GitHub Actions workflow scaffolding (`templates/scripts/`, `templates/workflows/`) | infra-engineer |
|
|
74
|
+
| ux-scaffold | Mockup project creation (html-lite, react-full) | ux-engineer |
|
|
75
|
+
| ux-theme-gen | Generate theme artifacts from DESIGN.md | ux-engineer, developer |
|
|
76
|
+
| memo-cli-usage | Read/write decisions to shared knowledge base | technical-writer, developer |
|
|
71
77
|
|
|
72
78
|
## Instructions
|
|
73
79
|
|
|
@@ -78,14 +84,20 @@ Platform coverage: `.github/agents/` and `.kiro/agents/` carry all ten. `.claude
|
|
|
78
84
|
| nextjs-pages-components | `**/app/**/*.tsx` | Next.js + React conventions |
|
|
79
85
|
| git-guard-notice | Always (Kiro) | Git invariants reminder |
|
|
80
86
|
|
|
87
|
+
`nextjs-pages-components` has a Claude gap: there is no automatic Claude delivery mechanism (no glob-scoped auto-load, no nested-`CLAUDE.md` scaffolding) — Claude Code consumers must manually copy the conventions into their app's nested `CLAUDE.md`. See `CLAUDE.md`'s "Domain-Specific Conventions" section.
|
|
88
|
+
|
|
81
89
|
## Hooks
|
|
82
90
|
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
|
86
|
-
|
|
|
91
|
+
Kiro (`.kiro/hooks/`) and Claude Code (`.claude/hooks/`, wired via `.claude/settings.json`) both ship these two `PreToolUse` hooks; Copilot has no hook system, so its enforcement is prompt-level only.
|
|
92
|
+
|
|
93
|
+
| Hook | Matcher (Claude Code) | Purpose |
|
|
94
|
+
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
95
|
+
| git-guard | `Bash`, plus (issue #178) the mutating GitHub MCP tool surface — `mcp__github__merge_pull_request`, `enable_pr_auto_merge`, `push_files`, `create_or_update_file`, `delete_file`, `create_branch` | Blocks pushes/merges/writes into the default branch (resolved dynamically, not hardcoded to `main`) — including `gh pr merge` with its base resolved via `gh pr view` (not a `--base` text check), `gh pr merge --admin` (blocked outright), `gh pr merge --auto` when the resolved base is the default branch, the raw-git escape of merging a story/issue branch into an integration branch, and the equivalent MCP-tool-call forms of all of the above (base/branch resolved from structured `tool_input` fields, not a command string) — plus non-Conventional commits, inline `gh --body`, and human-only tags |
|
|
96
|
+
| branch-guard | `Edit\|Write\|NotebookEdit` | Blocks write operations on default branch |
|
|
97
|
+
|
|
98
|
+
Hook enforcement is best-effort and fails open on unexpected errors, with one exception: if `git-guard` cannot verify a `gh pr merge`'s (or its MCP equivalent's) base branch — the `gh pr view` lookup fails (`gh` missing, unauthenticated, or a network error), or an MCP merge/auto-merge call omits enough `tool_input` to identify the PR at all — it fails **closed** and blocks the call, since an unverified base could be the default branch.
|
|
87
99
|
|
|
88
|
-
|
|
100
|
+
**Hooks are advisory, not the gate.** Every hook in this table is a best-effort, local, pattern-matching check over a command string or a structured tool-input shape — not a real parser, and not a completeness guarantee against every future command form or tool surface (a new MCP server, a future first-party tool) that could reopen the same class of gap. **GitHub branch protection on the default branch — require a PR, require ≥1 approving review, require passing status checks, disable force-push and branch deletion — is the actual, server-side, unbypassable-by-any-tool-surface control.** Hooks narrow the window and catch the common cases; they do not replace branch protection. Configure it per the README "Configure branch protection" step and `activity-init`'s Repository Setup section.
|
|
89
101
|
|
|
90
102
|
## General Agent Guidelines
|
|
91
103
|
|
|
@@ -94,7 +106,7 @@ All agents **MUST**:
|
|
|
94
106
|
- Create feature branches — never commit to default branch
|
|
95
107
|
- Use Conventional Commits (`feat`, `fix`, `chore`, `docs`, etc.)
|
|
96
108
|
- Create PRs for review — never self-merge into `main`; PRs targeting `main` require user approval
|
|
97
|
-
- Follow standards from `
|
|
109
|
+
- Follow standards from `tech.md`
|
|
98
110
|
- Reference GitHub Issues in branch names and commits
|
|
99
111
|
- Prefer `pnpm` over `npm`; use canonical scripts: `lint`, `format:check`, `typecheck`, `test`, `audit`, `validate`
|
|
100
112
|
- Enforce quality gates before completion
|
|
@@ -102,71 +114,12 @@ All agents **MUST**:
|
|
|
102
114
|
- Run `qa-engineer` at completion gate (record `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`)
|
|
103
115
|
- Run `verifier` audit (mandatory, non-skippable) before PR is ready; drift findings route to `product-engineer`
|
|
104
116
|
- Follow test-first design: write tests before implementation code
|
|
105
|
-
- If `memo-cli` is available: read/write entries per role
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
### architecture-change
|
|
112
|
-
|
|
113
|
-
The only mode granting write authority to the meta-repo. Agents **MUST NOT** write to the meta-repo outside this task type — applies to `product-engineer`, `developer`, `planner`, `housekeeping`, and all others.
|
|
114
|
-
|
|
115
|
-
#### Write Scope (RF-62)
|
|
116
|
-
|
|
117
|
-
**MAY** modify: `architecture.md`, `domains.md`, `glossary.md`, `conventions.md`, `catalog/flows/`.
|
|
118
|
-
|
|
119
|
-
**MUST NOT** modify: `catalog/components/*.json`, `catalog/index.yaml` — generated by CI (`dt extract` and `dt catalog build`), never hand-edited or agent-edited.
|
|
120
|
-
|
|
121
|
-
#### Generated-File Prohibition
|
|
122
|
-
|
|
123
|
-
`catalog/components/*.json` and `catalog/index.yaml` are generated by CI pipelines. No agent or human may edit these files directly.
|
|
124
|
-
|
|
125
|
-
#### ADR Requirement
|
|
126
|
-
|
|
127
|
-
Before opening any meta-repo PR under this task type, the agent **MUST** produce an Architecture Decision Record (ADR) containing: **Context** (why), **Decision** (what), **Consequences** (impact), and **Alternatives considered** (rejected approaches). The ADR **MUST** be committed as part of the PR.
|
|
128
|
-
|
|
129
|
-
#### Human Approval Gate
|
|
130
|
-
|
|
131
|
-
PRs from this task type targeting the meta-repo **REQUIRE** explicit human review and approval. No agent may auto-merge an `architecture-change` PR into the default branch.
|
|
132
|
-
|
|
133
|
-
#### Exclusion Rule (RF-64)
|
|
134
|
-
|
|
135
|
-
Agents **MUST NOT** write to the meta-repo outside the `architecture-change` task type. Refuse with:
|
|
136
|
-
|
|
137
|
-
> "Meta-repo writes require the `architecture-change` task type. Create an architecture-change task to modify these files."
|
|
138
|
-
|
|
139
|
-
---
|
|
140
|
-
|
|
141
|
-
## Cross-Repo Partitioning (RF-63)
|
|
142
|
-
|
|
143
|
-
When a scoping step identifies more than one `primary` component, the feature spans multiple repositories and the agent **MUST** partition the work into per-repo sub-tasks.
|
|
144
|
-
|
|
145
|
-
### Partitioning Procedure
|
|
146
|
-
|
|
147
|
-
1. **Detection:** If `scope.primary` contains >1 component, partition is **REQUIRED**.
|
|
148
|
-
2. **One sub-task per repo:** Each `primary` component becomes its own sub-task, scoped exclusively to that component's repository.
|
|
149
|
-
3. **Partition proposal:** When a partition proposal is available from `dt scope gate` (G1 abort, exit 7), the agent **SHOULD** use it as the basis for the partition. When no proposal exists, the agent **MUST** apply the same rules manually.
|
|
150
|
-
|
|
151
|
-
### Contract-as-Interface
|
|
152
|
-
|
|
153
|
-
Each sub-task uses the **boundary contract** (with a target version) as its interface. Acceptance criteria **MUST** reference the contract definition, **not** the foreign repo's internal implementation.
|
|
154
|
-
|
|
155
|
-
### Ordering Rule
|
|
156
|
-
|
|
157
|
-
Sub-tasks **MUST** be ordered producer-before-consumers: the provider (producer) implements its contract first. Consumer sub-tasks implement adaptation to the contract after the provider sub-task is complete.
|
|
158
|
-
|
|
159
|
-
### Low-Payload Elevation Guard
|
|
160
|
-
|
|
161
|
-
A boundary contract with `payload_confidence: low` **MUST** be raised to at least `medium` before use as an acceptance boundary. This is achieved by Re-running extraction (`dt extract`) with improved source hints, or Manual confirmation of the payload shape by a human reviewer.
|
|
162
|
-
|
|
163
|
-
Until elevated, the agent **MUST NOT** use it as an acceptance interface and **MUST** block the sub-task with:
|
|
164
|
-
|
|
165
|
-
> "Boundary contract `<contract-id>` has `payload_confidence: low`. Re-run extraction or manually confirm the payload shape before using it as an acceptance boundary."
|
|
166
|
-
|
|
167
|
-
### Single-Primary — No Partition
|
|
168
|
-
|
|
169
|
-
When `scope.primary` contains exactly 1 component, no partitioning is needed. The feature is single-repo and proceeds normally.
|
|
117
|
+
- If `memo-cli` is available: read/write entries per role, naming `--bank <id>` literally on every command (never `--bank $MEMO_BANK`), and report every write as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — never drop a failure silently
|
|
118
|
+
- Keep `docs/roadmap.md` current: `product-engineer` reads it at session start and adds a row per PRD phase/wave; `planner` reads it in Phase 0 and updates the delivered rows in the consolidated PR; `verifier` reports a mismatch with merged work as an advisory finding
|
|
119
|
+
- **Foundation documents: resolve the new name, fall back to the old one.** The canonical names are `docs/product.md` and `docs/tech.md`. A repository installed before the rename still carries `docs/product-context.md` and `docs/technical-guidelines.md`, and `dev-tasks update` never renames a consumer-owned file on its own. So when **reading** a foundation document, resolve the new name first and fall back to the old one only when the new name is absent; when **writing**, always write the new name. Propose `dev-tasks migrate docs` on encountering an old name. This applies to every agent and skill that reads these documents, for one release cycle (FR-45)
|
|
120
|
+
- Deliver a runbook in the **same PR** as any new or materially changed script under `templates/scripts/`, workflow under `templates/workflows/` or `.github/workflows/`, or `infra-engineer` change kind (FR-49a). Updating an existing runbook satisfies this
|
|
121
|
+
- Route a docs-structure failure in `validate` to `technical-writer`, never to `housekeeping` (FR-51): `technical-writer` owns documentation structure and content
|
|
122
|
+
- Treat a blocked guard as a decision, not an obstacle: when a hook blocks a tool call, surface the block verbatim, stop that line of work, and **MUST NOT** attempt an alternative command, tool surface, or sequence that achieves the same effect the block just prevented. Using a legitimate alternate mechanism for an unrelated, non-triggering purpose (e.g. `Read` instead of `grep`, `Write` instead of a shell heredoc) is not a route-around and remains allowed
|
|
170
123
|
|
|
171
124
|
---
|
|
172
125
|
|
|
@@ -0,0 +1,126 @@
|
|
|
1
|
+
# dev-tasks
|
|
2
|
+
|
|
3
|
+
Portable, repo-installed workflow harness for structured, PRD-driven AI-assisted development. Agents orchestrate the workflow end-to-end with branch discipline, test-first design, and GitHub-as-source-of-truth.
|
|
4
|
+
|
|
5
|
+
## Contracts
|
|
6
|
+
|
|
7
|
+
| File | Owner | Purpose |
|
|
8
|
+
| ------------- | ------------- | ---------------------------------------------- |
|
|
9
|
+
| `/DESIGN.md` | `ux-engineer` | Canonical design-system tokens and UI guidance |
|
|
10
|
+
| `/TESTING.md` | `qa-engineer` | Layer taxonomy, runners, thresholds, fixtures |
|
|
11
|
+
| `docs/roadmap.md` | `product-engineer` | PRD phases/waves: done, in progress, missing |
|
|
12
|
+
|
|
13
|
+
If `/DESIGN.md` is missing and scope includes UI work, agents **MUST** create a baseline before finalizing design-dependent outputs. An unfilled `/TESTING.md` placeholder means "no standard established", never permission.
|
|
14
|
+
|
|
15
|
+
## Taxonomy
|
|
16
|
+
|
|
17
|
+
| Concept | Purpose | Loaded When |
|
|
18
|
+
| --------------- | -------------------------------------------- | ----------------------- |
|
|
19
|
+
| **Agent** | Autonomous role with decisions and handoffs | Invoked by name |
|
|
20
|
+
| **Skill** | Reusable on-demand procedure | On demand by agent |
|
|
21
|
+
| **Instruction** | Scoped rule auto-applied to matching context | Auto-applied by runtime |
|
|
22
|
+
|
|
23
|
+
## Agents
|
|
24
|
+
|
|
25
|
+
| Agent | Purpose |
|
|
26
|
+
| -------------------- | --------------------------------------------------------------------------------------------------------- |
|
|
27
|
+
| **product-engineer** | Preparation — PRD, spec, stories, plan. Owns drift-reconciliation. |
|
|
28
|
+
| **developer** | Execution — implements from task lists with mandatory verifier audit pre-PR. |
|
|
29
|
+
| **planner** | Multi-story orchestration with dependency ordering and integration PR. |
|
|
30
|
+
| **technical-writer** | Autonomous documentation maintenance. **Owns docs structure and content**, including `docs/runbooks/`. |
|
|
31
|
+
| **housekeeping** | Lint, type, and test-wiring fixes. Does **not** organize documentation. |
|
|
32
|
+
| **github-ops** | GitHub consistency — issues, PRs, branches, labels, milestones, merge authority. |
|
|
33
|
+
| **ux-engineer** | UX prototyping, DESIGN.md ownership, mockup generation. |
|
|
34
|
+
| **qa-engineer** | Testing standard, test authoring, coverage/gap reporting. |
|
|
35
|
+
| **researcher** | Bounded codebase investigation producing structured research artifacts. |
|
|
36
|
+
| **verifier** | Compliance test-plan design and post-implementation fidelity audit. |
|
|
37
|
+
| **infra-engineer** | Approval-gated, reversible, recorded infrastructure changes across AWS, fly.io, Supabase, and Cloudflare. |
|
|
38
|
+
|
|
39
|
+
Platform coverage: `.github/agents/` and `.kiro/agents/` carry all eleven. `.claude/agents/` carries eight — `planner`, `product-engineer`, and `infra-engineer` run as `.claude/commands/` (they need main-thread human-approval gates: per-step for `infra-engineer`, per-phase for the two orchestrators).
|
|
40
|
+
|
|
41
|
+
## Skills
|
|
42
|
+
|
|
43
|
+
### Activity Skills
|
|
44
|
+
|
|
45
|
+
| Skill | Purpose | Consumer |
|
|
46
|
+
| ---------------------------------------- | --------------------------------------------------------- | ---------------- |
|
|
47
|
+
| activity-init | Establish product context and technical guidelines | product-engineer |
|
|
48
|
+
| activity-refine | Issue refinement or full PRD creation | product-engineer |
|
|
49
|
+
| activity-grill | One-question-at-a-time, depth-first interview to a confirmed shared-understanding exit gate | product-engineer |
|
|
50
|
+
| activity-codebase-research | Bounded codebase investigation with structured artifact | researcher |
|
|
51
|
+
| activity-generate-spec | PRD to technical specification | product-engineer |
|
|
52
|
+
| activity-generate-stories | Spec to user stories with coverage validation | product-engineer |
|
|
53
|
+
| activity-publish-github | Publish stories as GitHub Issues | product-engineer |
|
|
54
|
+
| activity-e2e-test-design | E2E scenario generation from spec/stories | verifier |
|
|
55
|
+
| activity-contract-test-design | Contract and schema compatibility test strategy | verifier |
|
|
56
|
+
| activity-edge-case-refinement | Systematic edge-case discovery | verifier |
|
|
57
|
+
| activity-random-test-tactics | Randomized/fuzz/property test generation | verifier |
|
|
58
|
+
| activity-test-standards | Establish/maintain TESTING.md, detect harness defects | qa-engineer |
|
|
59
|
+
| activity-test-implementation | Author Layer 1-2 tests with security-negative category | qa-engineer |
|
|
60
|
+
| activity-integration-test-implementation | Layer 2.5 tests against real databases | qa-engineer |
|
|
61
|
+
| activity-e2e-test-implementation | Playwright E2E from verifier scenario tables | qa-engineer |
|
|
62
|
+
| activity-coverage-gap-analysis | Coverage measurement or structural gap analysis | qa-engineer |
|
|
63
|
+
| activity-drift-reconciliation | Route drift findings to task expansion or spec write-back | product-engineer |
|
|
64
|
+
|
|
65
|
+
### Operational Skills
|
|
66
|
+
|
|
67
|
+
| Skill | Purpose | Consumer |
|
|
68
|
+
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
|
|
69
|
+
| git-ops | Branch management, rebase, merge, conflict resolution | developer, planner |
|
|
70
|
+
| aws-ops | AWS CLI command sets, tiers, cost, backup/revert, log table | infra-engineer |
|
|
71
|
+
| fly-ops | flyctl command sets, tiers, cost, backup/revert, log table | infra-engineer |
|
|
72
|
+
| supabase-ops | Supabase CLI command sets, `db diff` flow, drift rule, backup/revert, log table | infra-engineer |
|
|
73
|
+
| deploy-ops | Deploy script contract, environment mapping, tag policy, deploy-target framing, and GitHub Actions workflow scaffolding (`templates/scripts/`, `templates/workflows/`) | infra-engineer |
|
|
74
|
+
| ux-scaffold | Mockup project creation (html-lite, react-full) | ux-engineer |
|
|
75
|
+
| ux-theme-gen | Generate theme artifacts from DESIGN.md | ux-engineer, developer |
|
|
76
|
+
| memo-cli-usage | Read/write decisions to shared knowledge base | technical-writer, developer |
|
|
77
|
+
|
|
78
|
+
## Instructions
|
|
79
|
+
|
|
80
|
+
| Instruction | Scope | Purpose |
|
|
81
|
+
| ----------------------- | -------------------------- | -------------------------------------------------- |
|
|
82
|
+
| plan | `workstream/**` | Convert stories/issues into task lists |
|
|
83
|
+
| implement | `workstream/**/tasks-*.md` | Execute task list with branching and PR discipline |
|
|
84
|
+
| nextjs-pages-components | `**/app/**/*.tsx` | Next.js + React conventions |
|
|
85
|
+
| git-guard-notice | Always (Kiro) | Git invariants reminder |
|
|
86
|
+
|
|
87
|
+
`nextjs-pages-components` has a Claude gap: there is no automatic Claude delivery mechanism (no glob-scoped auto-load, no nested-`CLAUDE.md` scaffolding) — Claude Code consumers must manually copy the conventions into their app's nested `CLAUDE.md`. See `CLAUDE.md`'s "Domain-Specific Conventions" section.
|
|
88
|
+
|
|
89
|
+
## Hooks
|
|
90
|
+
|
|
91
|
+
Kiro (`.kiro/hooks/`) and Claude Code (`.claude/hooks/`, wired via `.claude/settings.json`) both ship these two `PreToolUse` hooks; Copilot has no hook system, so its enforcement is prompt-level only.
|
|
92
|
+
|
|
93
|
+
| Hook | Matcher (Claude Code) | Purpose |
|
|
94
|
+
| ------------ | ------------------------ | ---------------------------------------------------------------------------- |
|
|
95
|
+
| git-guard | `Bash`, plus (issue #178) the mutating GitHub MCP tool surface — `mcp__github__merge_pull_request`, `enable_pr_auto_merge`, `push_files`, `create_or_update_file`, `delete_file`, `create_branch` | Blocks pushes/merges/writes into the default branch (resolved dynamically, not hardcoded to `main`) — including `gh pr merge` with its base resolved via `gh pr view` (not a `--base` text check), `gh pr merge --admin` (blocked outright), `gh pr merge --auto` when the resolved base is the default branch, the raw-git escape of merging a story/issue branch into an integration branch, and the equivalent MCP-tool-call forms of all of the above (base/branch resolved from structured `tool_input` fields, not a command string) — plus non-Conventional commits, inline `gh --body`, and human-only tags |
|
|
96
|
+
| branch-guard | `Edit\|Write\|NotebookEdit` | Blocks write operations on default branch |
|
|
97
|
+
|
|
98
|
+
Hook enforcement is best-effort and fails open on unexpected errors, with one exception: if `git-guard` cannot verify a `gh pr merge`'s (or its MCP equivalent's) base branch — the `gh pr view` lookup fails (`gh` missing, unauthenticated, or a network error), or an MCP merge/auto-merge call omits enough `tool_input` to identify the PR at all — it fails **closed** and blocks the call, since an unverified base could be the default branch.
|
|
99
|
+
|
|
100
|
+
**Hooks are advisory, not the gate.** Every hook in this table is a best-effort, local, pattern-matching check over a command string or a structured tool-input shape — not a real parser, and not a completeness guarantee against every future command form or tool surface (a new MCP server, a future first-party tool) that could reopen the same class of gap. **GitHub branch protection on the default branch — require a PR, require ≥1 approving review, require passing status checks, disable force-push and branch deletion — is the actual, server-side, unbypassable-by-any-tool-surface control.** Hooks narrow the window and catch the common cases; they do not replace branch protection. Configure it per the README "Configure branch protection" step and `activity-init`'s Repository Setup section.
|
|
101
|
+
|
|
102
|
+
## General Agent Guidelines
|
|
103
|
+
|
|
104
|
+
All agents **MUST**:
|
|
105
|
+
|
|
106
|
+
- Create feature branches — never commit to default branch
|
|
107
|
+
- Use Conventional Commits (`feat`, `fix`, `chore`, `docs`, etc.)
|
|
108
|
+
- Create PRs for review — never self-merge into `main`; PRs targeting `main` require user approval
|
|
109
|
+
- Follow standards from `tech.md`
|
|
110
|
+
- Reference GitHub Issues in branch names and commits
|
|
111
|
+
- Prefer `pnpm` over `npm`; use canonical scripts: `lint`, `format:check`, `typecheck`, `test`, `audit`, `validate`
|
|
112
|
+
- Enforce quality gates before completion
|
|
113
|
+
- Use `git-ops` for complex branch operations
|
|
114
|
+
- Run `qa-engineer` at completion gate (record `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`)
|
|
115
|
+
- Run `verifier` audit (mandatory, non-skippable) before PR is ready; drift findings route to `product-engineer`
|
|
116
|
+
- Follow test-first design: write tests before implementation code
|
|
117
|
+
- If `memo-cli` is available: read/write entries per role, naming `--bank <id>` literally on every command (never `--bank $MEMO_BANK`), and report every write as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — never drop a failure silently
|
|
118
|
+
- Keep `docs/roadmap.md` current: `product-engineer` reads it at session start and adds a row per PRD phase/wave; `planner` reads it in Phase 0 and updates the delivered rows in the consolidated PR; `verifier` reports a mismatch with merged work as an advisory finding
|
|
119
|
+
- **Foundation documents: resolve the new name, fall back to the old one.** The canonical names are `docs/product.md` and `docs/tech.md`. A repository installed before the rename still carries `docs/product-context.md` and `docs/technical-guidelines.md`, and `dev-tasks update` never renames a consumer-owned file on its own. So when **reading** a foundation document, resolve the new name first and fall back to the old one only when the new name is absent; when **writing**, always write the new name. Propose `dev-tasks migrate docs` on encountering an old name. This applies to every agent and skill that reads these documents, for one release cycle (FR-45)
|
|
120
|
+
- Deliver a runbook in the **same PR** as any new or materially changed script under `templates/scripts/`, workflow under `templates/workflows/` or `.github/workflows/`, or `infra-engineer` change kind (FR-49a). Updating an existing runbook satisfies this
|
|
121
|
+
- Route a docs-structure failure in `validate` to `technical-writer`, never to `housekeeping` (FR-51): `technical-writer` owns documentation structure and content
|
|
122
|
+
- Treat a blocked guard as a decision, not an obstacle: when a hook blocks a tool call, surface the block verbatim, stop that line of work, and **MUST NOT** attempt an alternative command, tool surface, or sequence that achieves the same effect the block just prevented. Using a legitimate alternate mechanism for an unrelated, non-triggering purpose (e.g. `Read` instead of `grep`, `Write` instead of a shell heredoc) is not a route-around and remains allowed
|
|
123
|
+
|
|
124
|
+
---
|
|
125
|
+
|
|
126
|
+
For workflow chains: [`docs/workflow-chains.md`](docs/workflow-chains.md). For architecture and invariants: [`docs/system-overview.md`](docs/system-overview.md). Full docs index: [`docs/README.md`](docs/README.md).
|