docs: HUB.codex.md に YAML 出力例を追加し TASKS 対応表を追加#603
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 49e201e670
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | `task_id` | 識別情報 `task_id` | 日付ベース連番をそのまま記載 | | ||
| | `source` | Notes（出典） | `orchestration/...#Phase...` 形式の参照を原文維持で記録 | | ||
| | `objective` | Objective | 1文で転記（意図は変えない） | | ||
| | `requirements` | Requirements | `behavior` / `constraints` / 受入基準へ展開 | |
There was a problem hiding this comment.
The new fixed mapping table omits I/O Contract for requirements, but this same document defines Requirements as including behavior, I/O contract, constraints, and acceptance criteria (手順 2). If automation follows this table as the source of truth, generated Task Seeds can systematically lose input/output contract details and become non-compliant with the template requirements.
Useful? React with 👍 / 👎.
| | `requirements` | Requirements | `behavior` / `constraints` / 受入基準へ展開 | | ||
| | `commands` | Local Commands / Commands | 検証コマンドを順序維持で列挙 | | ||
| | `dependencies` | Plan（着手条件） | 依存 Task ID を着手前提として明記 | | ||
| | `status` | メタデータ `status` | `draft|active|...|done` の許容値に正規化 | |
There was a problem hiding this comment.
This row is under a section labeled as a fixed transfer contract, but draft|active|...|done is not deterministic enough for tooling and leaves intermediate states undefined. In practice, HUB examples now emit values like planned and in_progress, so a generator implementing this rule cannot normalize statuses consistently without guessing, which risks producing inconsistent Task Seed metadata.
Useful? React with 👍 / 👎.
1 participant
Motivation
docs/TASKS.mdの必須項目の転記ルールを一元化して自動化パイプラインの安定化を図る目的がある。Description
workflow-cookbook/HUB.codex.mdの「出力例」を「出力例（YAML）」へ変更し、例に必須キーtask_id,source,objective,requirements,commands,dependencies,statusを揃えた。terraform apply -target=module.api_gatewayとstatus: plannedを追記し、sourceをorchestration/<path>.md#Phase.../#Stage...形式で追跡可能にする旨を明文化した。docs/TASKS.mdに HUB 出力キーと Task Seed の須項目との対応表（転記先と転記ルール）を追加し、どのキーがどこへ転記されるかを固定化した。Testing
git -C /workspace/Day8 diff --checkを実行してエラーなし（成功）。Codex Task