@mengde1231/rudder 0.6.20 → 0.6.22
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/README.md +148 -136
- package/bin/rudder.js +0 -0
- package/dist/migrations/manifests/0.4.0-beta.1.json +5 -5
- package/dist/migrations/manifests/0.5.14.json +9 -0
- package/dist/migrations/manifests/0.5.15.json +9 -0
- package/dist/migrations/manifests/0.5.16.json +9 -0
- package/dist/migrations/manifests/0.5.17.json +9 -0
- package/dist/migrations/manifests/0.5.19.json +9 -0
- package/dist/migrations/manifests/0.5.20.json +9 -0
- package/dist/migrations/manifests/0.5.21.json +9 -0
- package/dist/migrations/manifests/0.5.22.json +9 -0
- package/dist/migrations/manifests/0.5.23.json +9 -0
- package/dist/migrations/manifests/0.5.30.json +9 -0
- package/dist/migrations/manifests/0.6.1.json +9 -0
- package/dist/migrations/manifests/0.6.11.json +9 -0
- package/dist/migrations/manifests/0.6.20.json +9 -0
- package/dist/migrations/manifests/0.6.21.json +9 -0
- package/dist/migrations/manifests/0.6.22.json +9 -0
- package/dist/templates/codex/config.toml +30 -30
- package/dist/templates/common/bundled-skills/rudder-meta/references/customize-local/change-workflow.md +5 -4
- package/dist/templates/common/bundled-skills/rudder-meta/references/local-architecture/task-system.md +7 -2
- package/dist/templates/common/bundled-skills/rudder-spec-bootstarp/SKILL.md +41 -41
- package/dist/templates/common/bundled-skills/rudder-spec-bootstarp/references/mcp-setup.md +90 -90
- package/dist/templates/common/bundled-skills/rudder-spec-bootstarp/references/repository-analysis.md +59 -59
- package/dist/templates/common/bundled-skills/rudder-spec-bootstarp/references/spec-task-planning.md +61 -61
- package/dist/templates/common/bundled-skills/rudder-spec-bootstarp/references/spec-writing.md +70 -70
- package/dist/templates/common/commands/continue.md +9 -5
- package/dist/templates/common/commands/start.md +8 -8
- package/dist/templates/common/skills/brainstorm.md +28 -27
- package/dist/templates/common/skills/check.md +8 -1
- package/dist/templates/rudder/config.yaml +13 -2
- package/dist/templates/rudder/index.d.ts +1 -0
- package/dist/templates/rudder/index.d.ts.map +1 -1
- package/dist/templates/rudder/index.js +2 -0
- package/dist/templates/rudder/index.js.map +1 -1
- package/dist/templates/rudder/scripts/common/task_context.py +42 -1
- package/dist/templates/rudder/scripts/common/task_readiness.py +176 -0
- package/dist/templates/rudder/scripts/common/task_store.py +23 -36
- package/dist/templates/rudder/scripts/common/types.py +1 -0
- package/dist/templates/rudder/scripts/common/workflow_phase.py +45 -0
- package/dist/templates/rudder/scripts/task.py +45 -4
- package/dist/templates/rudder/workflow.md +75 -37
- package/dist/utils/task-json.d.ts +6 -0
- package/dist/utils/task-json.d.ts.map +1 -1
- package/dist/utils/task-json.js +6 -0
- package/dist/utils/task-json.js.map +1 -1
- package/package.json +26 -27
|
@@ -16,13 +16,19 @@ Provides:
|
|
|
16
16
|
get_phase_index - Extract the Phase Index section (no --step)
|
|
17
17
|
get_step - Extract a single step (#### X.X) section
|
|
18
18
|
filter_platform - Strip platform blocks that don't include the given name
|
|
19
|
+
requires_task_context - Shared create/start JSONL policy for the invoking mode
|
|
19
20
|
"""
|
|
20
21
|
|
|
21
22
|
from __future__ import annotations
|
|
22
23
|
|
|
24
|
+
import os
|
|
23
25
|
import re
|
|
26
|
+
from pathlib import Path
|
|
27
|
+
from typing import get_args
|
|
24
28
|
|
|
29
|
+
from .cli_adapter import Platform
|
|
25
30
|
from .paths import DIR_WORKFLOW, get_repo_root
|
|
31
|
+
from .rudder_config import read_rudder_config
|
|
26
32
|
|
|
27
33
|
|
|
28
34
|
def _workflow_md_path():
|
|
@@ -171,6 +177,45 @@ def resolve_effective_platform(platform: str, config: dict) -> str:
|
|
|
171
177
|
return platform
|
|
172
178
|
|
|
173
179
|
|
|
180
|
+
# Keep the platform directories here so task creation and readiness use the
|
|
181
|
+
# same policy. Shared .agents/skills is not a platform-specific signal.
|
|
182
|
+
_SUBAGENT_CONFIG_DIRS: tuple[tuple[str, str], ...] = (
|
|
183
|
+
("claude", ".claude"),
|
|
184
|
+
("cursor", ".cursor"),
|
|
185
|
+
("codex", ".codex"),
|
|
186
|
+
("kiro", ".kiro"),
|
|
187
|
+
("gemini", ".gemini"),
|
|
188
|
+
("opencode", ".opencode"),
|
|
189
|
+
("qoder", ".qoder"),
|
|
190
|
+
("codebuddy", ".codebuddy"),
|
|
191
|
+
("droid", ".factory"),
|
|
192
|
+
("copilot", ".github/copilot"),
|
|
193
|
+
("pi", ".pi"),
|
|
194
|
+
)
|
|
195
|
+
_INLINE_PLATFORMS = {"codex-inline", "kilo", "antigravity", "windsurf"}
|
|
196
|
+
|
|
197
|
+
|
|
198
|
+
def requires_task_context(repo_root: Path, platform: str | None = None) -> bool:
|
|
199
|
+
"""Whether this invocation needs curated implement/check JSONL context.
|
|
200
|
+
|
|
201
|
+
Explicit --platform wins over RUDDER_PLATFORM. Without either, preserve
|
|
202
|
+
directory-based detection conservatively: any configured sub-agent mode
|
|
203
|
+
requires context. Mixed-platform repositories should pass --platform so a
|
|
204
|
+
Codex inline session cannot inherit another platform's requirements.
|
|
205
|
+
"""
|
|
206
|
+
config = read_rudder_config(repo_root)
|
|
207
|
+
selected = platform or os.environ.get("RUDDER_PLATFORM", "").strip().lower()
|
|
208
|
+
if selected:
|
|
209
|
+
if selected not in get_args(Platform):
|
|
210
|
+
raise ValueError(f"Unsupported platform: {selected}")
|
|
211
|
+
return resolve_effective_platform(selected, config) not in _INLINE_PLATFORMS
|
|
212
|
+
return any(
|
|
213
|
+
(repo_root / config_dir).is_dir()
|
|
214
|
+
and resolve_effective_platform(name, config) not in _INLINE_PLATFORMS
|
|
215
|
+
for name, config_dir in _SUBAGENT_CONFIG_DIRS
|
|
216
|
+
)
|
|
217
|
+
|
|
218
|
+
|
|
174
219
|
def filter_platform(content: str, platform: str) -> str:
|
|
175
220
|
"""Keep lines outside any `[...]` block + lines inside blocks that include platform.
|
|
176
221
|
|
|
@@ -4,11 +4,12 @@
|
|
|
4
4
|
Task Management Script.
|
|
5
5
|
|
|
6
6
|
Usage:
|
|
7
|
-
python3 task.py create "<title>" [--slug <name>] [--assignee <dev>] [--priority P0|P1|P2|P3] [--parent <dir>] [--package <pkg>]
|
|
7
|
+
python3 task.py create "<title>" [--slug <name>] [--assignee <dev>] [--priority P0|P1|P2|P3] [--parent <dir>] [--package <pkg>] [--platform <platform>]
|
|
8
8
|
python3 task.py add-context <dir> <file> <path> [reason] # Add jsonl entry
|
|
9
9
|
python3 task.py validate <dir> # Validate jsonl files
|
|
10
|
+
python3 task.py confirm <dir> # Confirm PRD requirements
|
|
10
11
|
python3 task.py list-context <dir> # List jsonl entries
|
|
11
|
-
python3 task.py start <dir>
|
|
12
|
+
python3 task.py start <dir> [--platform <platform>] # Validate readiness and set active task
|
|
12
13
|
python3 task.py current [--source] # Show active task
|
|
13
14
|
python3 task.py finish # Clear active task
|
|
14
15
|
python3 task.py set-branch <dir> <branch> # Set git branch
|
|
@@ -25,7 +26,9 @@ from __future__ import annotations
|
|
|
25
26
|
|
|
26
27
|
import argparse
|
|
27
28
|
import sys
|
|
29
|
+
from typing import get_args
|
|
28
30
|
|
|
31
|
+
from common.cli_adapter import Platform
|
|
29
32
|
from common.log import Colors, colored
|
|
30
33
|
from common.paths import (
|
|
31
34
|
DIR_WORKFLOW,
|
|
@@ -58,9 +61,11 @@ from common.task_store import (
|
|
|
58
61
|
)
|
|
59
62
|
from common.task_context import (
|
|
60
63
|
cmd_add_context,
|
|
64
|
+
cmd_confirm,
|
|
61
65
|
cmd_validate,
|
|
62
66
|
cmd_list_context,
|
|
63
67
|
)
|
|
68
|
+
from common.task_readiness import validate_task_readiness
|
|
64
69
|
|
|
65
70
|
|
|
66
71
|
# =============================================================================
|
|
@@ -92,6 +97,31 @@ def cmd_start(args: argparse.Namespace) -> int:
|
|
|
92
97
|
|
|
93
98
|
task_json_path = full_path / FILE_TASK_JSON
|
|
94
99
|
|
|
100
|
+
if not task_json_path.is_file():
|
|
101
|
+
print(colored(f"Error: task.json not found at {full_path}", Colors.RED))
|
|
102
|
+
return 1
|
|
103
|
+
|
|
104
|
+
# Only planning -> implementation is gated. Re-running start for an
|
|
105
|
+
# already active task remains idempotent for existing sessions.
|
|
106
|
+
task_data = read_json(task_json_path)
|
|
107
|
+
if not task_data:
|
|
108
|
+
print(colored(f"Error: task.json is invalid at {full_path}", Colors.RED))
|
|
109
|
+
return 1
|
|
110
|
+
if task_data and task_data.get("status") == "planning":
|
|
111
|
+
try:
|
|
112
|
+
readiness_errors = validate_task_readiness(
|
|
113
|
+
full_path, repo_root, task_data, getattr(args, "platform", None),
|
|
114
|
+
)
|
|
115
|
+
except ValueError as exc:
|
|
116
|
+
print(colored(f"Error: {exc}", Colors.RED))
|
|
117
|
+
return 1
|
|
118
|
+
if readiness_errors:
|
|
119
|
+
print(colored("Task is not ready for implementation:", Colors.RED))
|
|
120
|
+
for error in readiness_errors:
|
|
121
|
+
print(f" - {error}")
|
|
122
|
+
print("Hint: complete the PRD, run task.py confirm, then retry task.py start.")
|
|
123
|
+
return 1
|
|
124
|
+
|
|
95
125
|
if not resolve_context_key():
|
|
96
126
|
# Degraded mode: no session identity available.
|
|
97
127
|
# Hook didn't inject RUDDER_CONTEXT_ID (common on Windows + Claude Code,
|
|
@@ -131,7 +161,7 @@ def cmd_start(args: argparse.Namespace) -> int:
|
|
|
131
161
|
print(colored("✓ Status: planning → in_progress", Colors.GREEN))
|
|
132
162
|
|
|
133
163
|
print()
|
|
134
|
-
print(colored("
|
|
164
|
+
print(colored("Task selected. Follow the workflow for the current execution mode.", Colors.BLUE))
|
|
135
165
|
|
|
136
166
|
run_task_hooks("after_start", task_json_path, repo_root)
|
|
137
167
|
return 0
|
|
@@ -306,11 +336,13 @@ def show_usage() -> None:
|
|
|
306
336
|
Usage:
|
|
307
337
|
python3 task.py create <title> Create new task directory
|
|
308
338
|
python3 task.py create <title> --package <pkg> Create task for a specific package
|
|
339
|
+
python3 task.py create <title> --platform codex Create using Codex dispatch mode
|
|
309
340
|
python3 task.py create <title> --parent <dir> Create task as child of parent
|
|
310
341
|
python3 task.py add-context <dir> <jsonl> <path> [reason] Add entry to jsonl
|
|
311
342
|
python3 task.py validate <dir> Validate jsonl files
|
|
343
|
+
python3 task.py confirm <dir> Confirm requirements and PRD
|
|
312
344
|
python3 task.py list-context <dir> List jsonl entries
|
|
313
|
-
python3 task.py start <dir>
|
|
345
|
+
python3 task.py start <dir> [--platform <platform>] Validate readiness and set active task
|
|
314
346
|
python3 task.py current [--source] Show active task
|
|
315
347
|
python3 task.py finish Clear active task
|
|
316
348
|
python3 task.py set-branch <dir> <branch> Set git branch
|
|
@@ -398,6 +430,8 @@ def main() -> int:
|
|
|
398
430
|
p_create.add_argument("--description", "-d", help="Task description")
|
|
399
431
|
p_create.add_argument("--parent", help="Parent task directory (establishes subtask link)")
|
|
400
432
|
p_create.add_argument("--package", help="Package name for monorepo projects")
|
|
433
|
+
p_create.add_argument("--platform", choices=get_args(Platform),
|
|
434
|
+
help="Invoking platform; determines whether to seed JSONL context")
|
|
401
435
|
|
|
402
436
|
# add-context
|
|
403
437
|
p_add = subparsers.add_parser("add-context", help="Add context entry")
|
|
@@ -410,6 +444,10 @@ def main() -> int:
|
|
|
410
444
|
p_validate = subparsers.add_parser("validate", help="Validate context files")
|
|
411
445
|
p_validate.add_argument("dir", help="Task directory")
|
|
412
446
|
|
|
447
|
+
# confirm
|
|
448
|
+
p_confirm = subparsers.add_parser("confirm", help="Confirm task requirements")
|
|
449
|
+
p_confirm.add_argument("dir", help="Task directory")
|
|
450
|
+
|
|
413
451
|
# list-context
|
|
414
452
|
p_listctx = subparsers.add_parser("list-context", help="List context entries")
|
|
415
453
|
p_listctx.add_argument("dir", help="Task directory")
|
|
@@ -417,6 +455,8 @@ def main() -> int:
|
|
|
417
455
|
# start
|
|
418
456
|
p_start = subparsers.add_parser("start", help="Set active task")
|
|
419
457
|
p_start.add_argument("dir", help="Task directory")
|
|
458
|
+
p_start.add_argument("--platform", choices=get_args(Platform),
|
|
459
|
+
help="Invoking platform; determines JSONL readiness requirements")
|
|
420
460
|
|
|
421
461
|
# current
|
|
422
462
|
p_current = subparsers.add_parser("current", help="Show active task")
|
|
@@ -475,6 +515,7 @@ def main() -> int:
|
|
|
475
515
|
"create": cmd_create,
|
|
476
516
|
"add-context": cmd_add_context,
|
|
477
517
|
"validate": cmd_validate,
|
|
518
|
+
"confirm": cmd_confirm,
|
|
478
519
|
"list-context": cmd_list_context,
|
|
479
520
|
"start": cmd_start,
|
|
480
521
|
"current": cmd_current,
|
|
@@ -43,8 +43,8 @@ Every task has its own directory under `.rudder/tasks/{MM-DD-name}/` holding `pr
|
|
|
43
43
|
|
|
44
44
|
```bash
|
|
45
45
|
# Task lifecycle
|
|
46
|
-
python3 ./.rudder/scripts/task.py create "<title>" [--slug <name>] [--parent <dir>]
|
|
47
|
-
python3 ./.rudder/scripts/task.py start <name>
|
|
46
|
+
python3 ./.rudder/scripts/task.py create "<title>" [--slug <name>] [--parent <dir>] --platform <platform>
|
|
47
|
+
python3 ./.rudder/scripts/task.py start <name> --platform <platform> # validate readiness and enter implementation
|
|
48
48
|
python3 ./.rudder/scripts/task.py current --source # show active task and source
|
|
49
49
|
python3 ./.rudder/scripts/task.py finish # clear active task (triggers after_finish hooks)
|
|
50
50
|
python3 ./.rudder/scripts/task.py archive <name> # move to archive/{year-month}/
|
|
@@ -73,7 +73,9 @@ python3 ./.rudder/scripts/task.py create-pr [name] [--dry-run]
|
|
|
73
73
|
|
|
74
74
|
> Run `python3 ./.rudder/scripts/task.py --help` to see the authoritative, up-to-date list.
|
|
75
75
|
|
|
76
|
-
|
|
76
|
+
Replace `<platform>` with the invoking CLI flag (e.g. `codex`, `claude`, `cursor`). Creation and startup share the same context policy: explicit `--platform` takes precedence over `RUDDER_PLATFORM`; without either, any configured sub-agent mode requires JSONL. Pass the invoking platform in mixed-platform repositories. Codex resolves `codex.dispatch_mode` (default `inline`); inline execution does not require JSONL even when old seed files exist, while sub-agent execution requires both curated context files even when they are missing.
|
|
77
|
+
|
|
78
|
+
**Current-task mechanism**: `task.py create` creates the task directory and (when session identity is available) auto-sets the per-session active-task pointer so the planning breadcrumb fires immediately. After the final PRD is confirmed with `task.py confirm`, `task.py start` writes the same pointer (idempotent if already set) and flips `task.json.status` from `planning` to `in_progress`; it refuses to start when the PRD, confirmation hash, acceptance criteria, or applicable JSONL context is incomplete. State is stored under `.rudder/.runtime/sessions/`. If no context key is available, start still performs the readiness gate and then uses degraded mode without persisting a session pointer. `task.py finish` deletes the current session file (status unchanged). `task.py archive <task>` writes `status=completed`, moves the directory to `archive/`, and deletes any runtime session files that still point at the archived task.
|
|
77
79
|
|
|
78
80
|
### Workspace System
|
|
79
81
|
|
|
@@ -147,12 +149,28 @@ Phase 2: Execute → write code and pass quality checks
|
|
|
147
149
|
Phase 3: Finish → distill lessons + wrap-up
|
|
148
150
|
```
|
|
149
151
|
|
|
152
|
+
### Request routing (before every phase)
|
|
153
|
+
|
|
154
|
+
Decide what the user is asking for before following an active task's phase. Task boundaries follow **business objective and acceptance scope**, not the conversation, module, file count, or mere presence of an active pointer.
|
|
155
|
+
|
|
156
|
+
Apply these rules in order:
|
|
157
|
+
|
|
158
|
+
1. **Direct answer/action**: questions, explanations, code inspection, scheduler/Cron administration, and commit-message drafting do not create or advance a task. Only provide the requested output/action; a request for commit wording is not permission to commit or archive. Developing a scheduled business feature still follows the rules below. Read depth and answer length do not determine whether a task is needed.
|
|
159
|
+
2. **Reuse related unfinished work**: read the candidate task's goal, requirements, acceptance criteria, and status. Supplements, corrections, fixes before acceptance, continuation, and moving from design to development reuse that task and update relevant artifacts. Check current and other unfinished tasks as needed; same session/module alone does not establish relevance. Reuse takes priority over treating a related correction as a separate quick edit. If ownership is genuinely ambiguous, ask one focused question.
|
|
160
|
+
3. **Direct low-risk edit**: a clear, local, low-risk independent change can be made directly with the relevant guidelines and smallest meaningful validation. No special bypass phrase is required. Assess behavior and contracts, not number of files; changes to permissions, data structures, API contracts, transactions, caches, or cross-module business rules need the task workflow.
|
|
161
|
+
4. **New tracked objective**: create a task for an independent business objective needing durable planning and its own acceptance outcome. An unrelated active task must not absorb it. Leave the previous task's artifacts/status intact; task creation can switch this session's pointer. For defects after a task was completed/archived, normally create a linked follow-up rather than rewriting historical acceptance.
|
|
162
|
+
|
|
163
|
+
**Approval reuse**: an explicit instruction such as “implement this plan” / “按方案开发” approves the clearly agreed requirements. Record that approval with `task.py confirm` and proceed; do not ask the same question again at each phase. Ask only when a new business decision or a material scope/acceptance change needs user input. Implementation details do not need repeated approval. The existing PRD hash gate still applies: update the confirmation record while planning when the agreed PRD changes; never invent approval for new requirements.
|
|
164
|
+
|
|
150
165
|
<!-- Per-turn breadcrumb: shown when there is no active task (before Phase 1) -->
|
|
151
166
|
|
|
152
167
|
[workflow-state:no_task]
|
|
153
|
-
No active task.
|
|
154
|
-
|
|
155
|
-
**
|
|
168
|
+
No active task. Apply Request routing by business objective and acceptance scope.
|
|
169
|
+
For development requests, check related unfinished work (B) before choosing a direct independent edit (A) or creating a task (C).
|
|
170
|
+
**A Direct work** — questions, code inspection, scheduler administration, commit-message drafting, or clear/local/low-risk independent edits: answer or act directly with necessary validation; no task, no phase advancement, no file-count/read-depth limits. Commit wording alone never authorizes a Git commit.
|
|
171
|
+
**B Reuse** — supplements, corrections, fixes, continuation, or design-to-development serving an existing unfinished goal reuse that task and its PRD; same session/module alone is insufficient. Check unfinished tasks before creating another.
|
|
172
|
+
**C New task** — an independent objective needing durable planning and its own acceptance outcome gets a new task. Create → complete PRD and applicable context → confirm already-approved requirements → start with `--platform <platform>`. Do not repeat approval already given for the agreed plan.
|
|
173
|
+
An explicit per-turn bypass (e.g. "skip rudder", "no task", "直接改", "先别建任务") also allows the requested low-risk edit. It does not bypass necessary safety checks for database, API, permission, transaction, cache, or cross-module changes.
|
|
156
174
|
[/workflow-state:no_task]
|
|
157
175
|
|
|
158
176
|
### Phase 1: Plan
|
|
@@ -167,10 +185,11 @@ No active task. **A Direct answer** — pure Q&A / explanation / lookup / chat;
|
|
|
167
185
|
<!-- Per-turn breadcrumb: shown throughout Phase 1 (status='planning') -->
|
|
168
186
|
|
|
169
187
|
[workflow-state:planning]
|
|
188
|
+
First apply Request routing: questions/inspection/scheduler administration/commit wording are direct requests; related work reuses this task; an unrelated objective needs its own task unless it is a clear/local/low-risk direct edit. Never infer task ownership from session/module alone.
|
|
170
189
|
Load the `rudder-brainstorm` skill and iterate on prd.md with the user.
|
|
171
190
|
Phase 1.0.5 (conditional, once): if this task involves DDL operations (create/alter tables, add/drop columns, migration scripts), create `{TASK_DIR}/sql/` via `mkdir -p .rudder/tasks/<task-dir>/sql/`. Skip if no database changes.
|
|
172
191
|
Phase 1.3 (required, once): before `task.py start`, you MUST curate `implement.jsonl` and `check.jsonl` — list the spec / research files sub-agents need so they get the right context injected. You may skip only if the jsonl already has agent-curated entries (the seed `_example` row alone doesn't count).
|
|
173
|
-
Then run `task.py start <task-dir>` to flip status to in_progress.
|
|
192
|
+
Before `task.py start`, run `task.py confirm <task-dir>` after the user approves the final `prd.md`; an existing instruction to implement the agreed plan counts, so do not ask again. This records the PRD hash and blocks stale or unconfirmed requirements. Then run `task.py start <task-dir> --platform <platform>` to flip status to in_progress. PRD existence alone does not mean planning is complete.
|
|
174
193
|
[/workflow-state:planning]
|
|
175
194
|
|
|
176
195
|
<!-- Per-turn breadcrumb: shown throughout Phase 1 when codex.dispatch_mode=inline.
|
|
@@ -180,15 +199,16 @@ Then run `task.py start <task-dir>` to flip status to in_progress.
|
|
|
180
199
|
into a sub-agent. -->
|
|
181
200
|
|
|
182
201
|
[workflow-state:planning-inline]
|
|
202
|
+
First apply Request routing: questions/inspection/scheduler administration/commit wording are direct requests; related work reuses this task; an unrelated objective needs its own task unless it is a clear/local/low-risk direct edit. Never infer task ownership from session/module alone.
|
|
183
203
|
Load the `rudder-brainstorm` skill and iterate on prd.md with the user.
|
|
184
204
|
Phase 1.0.5 (conditional, once): if this task involves DDL operations (create/alter tables, add/drop columns, migration scripts), create `{TASK_DIR}/sql/` via `mkdir -p .rudder/tasks/<task-dir>/sql/`. Skip if no database changes.
|
|
185
205
|
Phase 1.3 jsonl curation is **skipped** in inline dispatch mode — the main session loads `rudder-before-dev` directly in Phase 2 and reads spec context itself, so there is no sub-agent to inject jsonl into.
|
|
186
|
-
Then run `task.py start <task-dir
|
|
206
|
+
Before `task.py start`, run `task.py confirm <task-dir>` after the user approves the final `prd.md`; an existing instruction to implement the agreed plan counts, so do not ask again. This records the PRD hash and blocks stale or unconfirmed requirements. Then run `task.py start <task-dir> --platform codex` to flip status to in_progress. Existing JSONL seed files do not block inline startup. PRD existence alone does not mean planning is complete.
|
|
187
207
|
[/workflow-state:planning-inline]
|
|
188
208
|
|
|
189
209
|
### Phase 2: Execute
|
|
190
|
-
- 2.1 Implement `[required · repeatable]`
|
|
191
|
-
- 2.2
|
|
210
|
+
- 2.1 Implement `[required · repeatable until complete]`
|
|
211
|
+
- 2.2 Verify `[required · after implementation; repeat only after fixes]`
|
|
192
212
|
- 2.3 Rollback `[on demand]`
|
|
193
213
|
|
|
194
214
|
<!-- Per-turn breadcrumb: shown while status='in_progress'.
|
|
@@ -198,7 +218,8 @@ Then run `task.py start <task-dir>` to flip status to in_progress.
|
|
|
198
218
|
commit, including Phase 3.3 spec update and Phase 3.4 commit. -->
|
|
199
219
|
|
|
200
220
|
[workflow-state:in_progress]
|
|
201
|
-
|
|
221
|
+
First apply Request routing: questions/inspection/scheduler administration/commit wording do not advance this task; related corrections/continuation reuse it; unrelated objectives get their own task unless they qualify for direct low-risk work. Same session/module does not establish relevance. Already-approved requirements do not need another approval.
|
|
222
|
+
**Flow**: finish all implementation work → rudder-check review → Verify (lint/type-check/tests/build) → fix all findings → rerun Verify if needed → conditional rudder-update-spec → commit (Phase 3.4) → `/rudder:finish-work`.
|
|
202
223
|
**Main-session default (no override)**: dispatch the `rudder-implement` / `rudder-check` sub-agents — the main agent does NOT edit code by default. Phase 3.4 commit (required, once): after rudder-update-spec, or whenever implementation is verifiably complete, the main agent **drives the commit** — run `git diff --stat` to show changes, state the proposed commit message, then check `code_auto_commit` in `.rudder/config.yaml`: if **false** (default), **ask the user for confirmation (Y/n)** before running `git commit`; if **true**, commit directly without prompting. Only after commit, suggest `/rudder:finish-work`. `/finish-work` refuses to run on a dirty working tree (paths outside `.rudder/workspace/` and `.rudder/tasks/`).
|
|
203
224
|
**Sub-agent self-exemption**: if you are already running as `rudder-implement`, implement directly from the loaded task context and do NOT spawn another `rudder-implement`; if you are already running as `rudder-check`, review/fix directly and do NOT spawn another `rudder-check`. The default dispatch rule applies to the main session only.
|
|
204
225
|
**Sub-agent dispatch protocol (all platforms, all sub-agents)**: When you spawn `rudder-implement` / `rudder-check` / `rudder-research`, your dispatch prompt **MUST** start with one line: `Active task: <task path from \`task.py current\`>`. No exceptions. On class-2 platforms (codex / copilot / gemini / qoder) the sub-agent depends on this line because there is no hook to inject task context. On class-1 platforms (claude / cursor / opencode / kiro / codebuddy / droid) the line is normally redundant — the hook injects context directly — but it serves as a critical fallback when the hook fails (Windows + Claude Code PreToolUse silent skip, `--continue` resume, fork distribution, hooks disabled, etc.). For `rudder-research`, the line tells the sub-agent which `{task_dir}/research/` to write into.
|
|
@@ -211,13 +232,14 @@ Then run `task.py start <task-dir>` to flip status to in_progress.
|
|
|
211
232
|
instead of dispatching sub-agents. -->
|
|
212
233
|
|
|
213
234
|
[workflow-state:in_progress-inline]
|
|
214
|
-
|
|
235
|
+
First apply Request routing: questions/inspection/scheduler administration/commit wording do not advance this task; related corrections/continuation reuse it; unrelated objectives get their own task unless they qualify for direct low-risk work. Same session/module does not establish relevance. Already-approved requirements do not need another approval.
|
|
236
|
+
**Flow** (inline mode): main session loads `rudder-before-dev` → main session finishes all code changes → main session loads `rudder-check` for the full task diff → Verify lint / type-check / tests / build → fix all findings → rerun Verify if needed → conditional `rudder-update-spec` → commit (Phase 3.4) → `/rudder:finish-work`.
|
|
215
237
|
**Main-session default (inline dispatch_mode)**: the main agent edits code directly. Do NOT dispatch `rudder-implement` / `rudder-check` sub-agents. Load the `rudder-before-dev` skill before writing code; load the `rudder-check` skill before reporting completion.
|
|
216
238
|
Phase 3.4 commit (required, once): after `rudder-update-spec`, or whenever implementation is verifiably complete, the main agent **drives the commit** — run `git diff --stat` to show changes, state the proposed commit message, then check `code_auto_commit` in `.rudder/config.yaml`: if **false** (default), **ask the user for confirmation (Y/n)** before running `git commit`; if **true**, commit directly without prompting. Only after commit, suggest `/rudder:finish-work`. `/finish-work` refuses to run on a dirty working tree (paths outside `.rudder/workspace/` and `.rudder/tasks/`).
|
|
217
239
|
[/workflow-state:in_progress-inline]
|
|
218
240
|
|
|
219
241
|
### Phase 3: Finish
|
|
220
|
-
- 3.1
|
|
242
|
+
- 3.1 Verify evidence `[folded into 2.2 and commit preamble]`
|
|
221
243
|
- 3.2 Debug retrospective `[on demand]`
|
|
222
244
|
- 3.3 Spec update `[conditional · once]`
|
|
223
245
|
- 3.4 Commit changes `[required · once]`
|
|
@@ -232,6 +254,7 @@ Phase 3.4 commit (required, once): after `rudder-update-spec`, or whenever imple
|
|
|
232
254
|
channel as the live blocks. -->
|
|
233
255
|
|
|
234
256
|
[workflow-state:completed]
|
|
257
|
+
First apply Request routing. Answer questions/inspection/commit-wording requests directly; do not attach independent new work to this completed task. Normally track post-completion defects as linked follow-ups.
|
|
235
258
|
Code committed via Phase 3.4; run `/rudder:finish-work` to wrap up (archive the task + record session).
|
|
236
259
|
If you reach this state with uncommitted code, return to Phase 3.4 first — `/finish-work` refuses to run on a dirty working tree.
|
|
237
260
|
`task.py archive` deletes any runtime session files that still point at the archived task.
|
|
@@ -239,14 +262,14 @@ If you reach this state with uncommitted code, return to Phase 3.4 first — `/f
|
|
|
239
262
|
|
|
240
263
|
### Rules
|
|
241
264
|
|
|
242
|
-
1.
|
|
265
|
+
1. Apply Request routing, establish task relevance, then identify the phase and next step
|
|
243
266
|
2. Run steps in order inside each Phase; `[required]` steps can't be skipped
|
|
244
267
|
3. Phases can roll back (e.g., Execute reveals a prd defect → return to Plan to fix, then re-enter Execute)
|
|
245
|
-
4.
|
|
268
|
+
4. Skip `[once]` steps only when their completion conditions hold. PRD existence alone is insufficient; require resolved requirements, current approval/confirmation, and both valid curated JSONL files when applicable.
|
|
246
269
|
|
|
247
270
|
### Skill Routing
|
|
248
271
|
|
|
249
|
-
|
|
272
|
+
After Request routing selects tracked work, use the skill/sub-agent routes below. Direct low-risk edits read relevant guidelines (via `rudder-before-dev` where available) and run the smallest meaningful validation; they do not enter task creation, sub-agent dispatch, or finish/commit phases automatically.
|
|
250
273
|
|
|
251
274
|
[Claude Code, Cursor, OpenCode, codex-sub-agent, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
252
275
|
|
|
@@ -254,7 +277,7 @@ When a user request matches one of these intents, load the corresponding skill (
|
|
|
254
277
|
|---|---|
|
|
255
278
|
| Wants a new feature / requirement unclear | `rudder-brainstorm` |
|
|
256
279
|
| About to write code / start implementing | Dispatch the `rudder-implement` sub-agent per Phase 2.1 |
|
|
257
|
-
| Finished
|
|
280
|
+
| Finished all implementation / want to verify | Dispatch the `rudder-check` sub-agent once per Phase 2.2 |
|
|
258
281
|
| Stuck / fixed same bug several times | `rudder-break-loop` |
|
|
259
282
|
| Spec needs update | `rudder-update-spec` |
|
|
260
283
|
|
|
@@ -268,7 +291,7 @@ When a user request matches one of these intents, load the corresponding skill (
|
|
|
268
291
|
|---|---|
|
|
269
292
|
| Wants a new feature / requirement unclear | `rudder-brainstorm` |
|
|
270
293
|
| About to write code / start implementing | `rudder-before-dev` (then implement directly in the main session) |
|
|
271
|
-
| Finished
|
|
294
|
+
| Finished all implementation / want to verify | `rudder-check` |
|
|
272
295
|
| Stuck / fixed same bug several times | `rudder-break-loop` |
|
|
273
296
|
| Spec needs update | `rudder-update-spec` |
|
|
274
297
|
|
|
@@ -283,7 +306,7 @@ When a user request matches one of these intents, load the corresponding skill (
|
|
|
283
306
|
| "This is simple, I'll just code it in the main thread" | Dispatching `rudder-implement` is the cheap path; skipping it tempts you to write code in the main thread and lose spec context — sub-agents get `implement.jsonl` injected, you don't |
|
|
284
307
|
| "I already thought it through in plan mode" | Plan-mode output lives in memory — sub-agents can't see it; must be persisted to prd.md |
|
|
285
308
|
| "I already know the spec" | The spec may have been updated since you last read it; the sub-agent gets the fresh copy, you may not |
|
|
286
|
-
| "
|
|
309
|
+
| "Check after every small change" | Check is a post-implementation gate; finish the complete change set first so the reviewer sees the real cross-file contract |
|
|
287
310
|
|
|
288
311
|
[/Claude Code, Cursor, OpenCode, codex-sub-agent, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
289
312
|
|
|
@@ -294,7 +317,7 @@ When a user request matches one of these intents, load the corresponding skill (
|
|
|
294
317
|
| "This is simple, just code it" | Simple tasks often grow complex; `rudder-before-dev` takes under a minute and loads the spec context you'll need |
|
|
295
318
|
| "I already thought it through in plan mode" | Plan-mode output lives in memory — must be persisted to prd.md before code |
|
|
296
319
|
| "I already know the spec" | The spec may have been updated since you last read it; read again |
|
|
297
|
-
| "
|
|
320
|
+
| "Check after every small change" | Check is a post-implementation gate; finish the complete change set first so the reviewer sees the real cross-file contract |
|
|
298
321
|
|
|
299
322
|
[/codex-inline, Kilo, Antigravity, Windsurf]
|
|
300
323
|
|
|
@@ -318,7 +341,7 @@ Goal: figure out what to build, produce a clear requirements doc and the context
|
|
|
318
341
|
Create the task directory (status enters `planning`, the session active-task pointer auto-targets the new task when session identity is available):
|
|
319
342
|
|
|
320
343
|
```bash
|
|
321
|
-
python3 ./.rudder/scripts/task.py create "<task title>" --slug <name>
|
|
344
|
+
python3 ./.rudder/scripts/task.py create "<task title>" --slug <name> --platform <platform>
|
|
322
345
|
```
|
|
323
346
|
|
|
324
347
|
`--slug` is the human-readable name only. Do **not** include the `MM-DD-` date prefix; `task.py create` adds that prefix automatically.
|
|
@@ -327,7 +350,7 @@ After this command succeeds, the per-turn breadcrumb auto-switches to `[workflow
|
|
|
327
350
|
|
|
328
351
|
⚠️ **Run only `create` here — do not also run `start`**. `start` flips status to `in_progress`, which switches the breadcrumb to the implementation phase before brainstorm + jsonl are done — the AI will silently skip them. Save `start` for step 1.4, after jsonl curation is complete.
|
|
329
352
|
|
|
330
|
-
Skip when
|
|
353
|
+
Skip creation only when the request belongs to a related unfinished task. Read its goal and acceptance scope before reusing it; a current pointer alone is not sufficient. Design-to-development work keeps the same task.
|
|
331
354
|
|
|
332
355
|
#### 1.0.5 Prepare SQL directory `[conditional · once]`
|
|
333
356
|
|
|
@@ -347,6 +370,8 @@ mkdir -p .rudder/tasks/<task-dir>/sql/
|
|
|
347
370
|
|
|
348
371
|
Load the `rudder-brainstorm` skill and explore requirements interactively with the user per the skill's guidance.
|
|
349
372
|
|
|
373
|
+
If the user already approved the clearly agreed plan, persist it and proceed without another approval question. Revisit only unresolved business decisions or material scope/acceptance changes.
|
|
374
|
+
|
|
350
375
|
The brainstorm skill will guide you to:
|
|
351
376
|
- Ask one question at a time
|
|
352
377
|
- Prefer researching over asking the user
|
|
@@ -425,7 +450,7 @@ python3 ./.rudder/scripts/task.py add-context "$TASK_DIR" check "<path>" "<reaso
|
|
|
425
450
|
|
|
426
451
|
Delete the seed `_example` line once real entries exist (optional — it's skipped automatically by consumers).
|
|
427
452
|
|
|
428
|
-
Skip when: `implement.jsonl`
|
|
453
|
+
Skip when: both `implement.jsonl` and `check.jsonl` already have valid agent-curated entries (seed rows alone do not count).
|
|
429
454
|
|
|
430
455
|
[/Claude Code, Cursor, OpenCode, codex-sub-agent, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
431
456
|
|
|
@@ -437,21 +462,23 @@ Skip this step. Context is loaded directly by the `rudder-before-dev` skill in P
|
|
|
437
462
|
|
|
438
463
|
#### 1.4 Activate task `[required · once]`
|
|
439
464
|
|
|
440
|
-
Once prd.md is complete and 1.3 jsonl curation is done,
|
|
465
|
+
Once prd.md is complete, the user has confirmed it, and 1.3 jsonl curation is done when applicable, confirm and activate the task:
|
|
441
466
|
|
|
442
467
|
```bash
|
|
443
|
-
python3 ./.rudder/scripts/task.py
|
|
468
|
+
python3 ./.rudder/scripts/task.py confirm <task-dir>
|
|
469
|
+
python3 ./.rudder/scripts/task.py start <task-dir> --platform <platform>
|
|
444
470
|
```
|
|
445
471
|
|
|
446
472
|
After this command succeeds, the breadcrumb auto-switches to `[workflow-state:in_progress]`, and the rest of Phase 2 / 3 follows.
|
|
447
473
|
|
|
448
|
-
|
|
474
|
+
Use the invoking platform; Codex inline skips JSONL curation and validation even if seed files remain, while sub-agent modes require both curated files. A readiness failure leaves the task in planning: resolve its reported PRD/approval/context blockers and retry. When session identity is unavailable, start still validates readiness and enters implementation in degraded mode without persisting a session pointer.
|
|
449
475
|
|
|
450
476
|
#### 1.5 Completion criteria
|
|
451
477
|
|
|
452
478
|
| Condition | Required |
|
|
453
479
|
|------|:---:|
|
|
454
480
|
| `prd.md` exists | ✅ |
|
|
481
|
+
| `prd.md` has acceptance criteria and no unresolved questions/conflicts | ✅ |
|
|
455
482
|
| User confirms requirements | ✅ |
|
|
456
483
|
| `task.py start` has been run (status = in_progress) | ✅ |
|
|
457
484
|
| `research/` has artifacts (complex tasks) | recommended |
|
|
@@ -459,7 +486,7 @@ If `task.py start` errors with a session-identity message (no context key from h
|
|
|
459
486
|
|
|
460
487
|
[Claude Code, Cursor, OpenCode, codex-sub-agent, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
461
488
|
|
|
462
|
-
| `implement.jsonl`
|
|
489
|
+
| Both `implement.jsonl` and `check.jsonl` have valid agent-curated entries (not just seed rows) | ✅ |
|
|
463
490
|
|
|
464
491
|
[/Claude Code, Cursor, OpenCode, codex-sub-agent, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
465
492
|
|
|
@@ -467,16 +494,18 @@ If `task.py start` errors with a session-identity message (no context key from h
|
|
|
467
494
|
|
|
468
495
|
## Phase 2: Execute
|
|
469
496
|
|
|
470
|
-
Goal: turn the
|
|
497
|
+
Goal: turn the confirmed PRD into code. Project syntax, build, lint, type-check,
|
|
498
|
+
and business acceptance tests are run after implementation during Phase 3;
|
|
499
|
+
`task.py start` performs readiness checks only and does not replace those checks.
|
|
471
500
|
|
|
472
|
-
#### 2.1 Implement `[required · repeatable]`
|
|
501
|
+
#### 2.1 Implement `[required · repeatable until complete]`
|
|
473
502
|
|
|
474
503
|
[Claude Code, Cursor, OpenCode, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
475
504
|
|
|
476
505
|
Spawn the implement sub-agent:
|
|
477
506
|
|
|
478
507
|
- **Agent type**: `rudder-implement`
|
|
479
|
-
- **Task description**: Implement
|
|
508
|
+
- **Task description**: Implement all requirements in prd.md, consulting materials under `{TASK_DIR}/research/`; continue until the complete change set is written and report implementation complete. Do not dispatch `rudder-check` or run the quality gate during this step.
|
|
480
509
|
- **Dispatch prompt guard**: Tell the spawned agent it is already the `rudder-implement` sub-agent and must implement directly, not spawn another `rudder-implement` / `rudder-check`.
|
|
481
510
|
|
|
482
511
|
The platform hook/plugin auto-handles:
|
|
@@ -490,7 +519,7 @@ The platform hook/plugin auto-handles:
|
|
|
490
519
|
Spawn the implement sub-agent:
|
|
491
520
|
|
|
492
521
|
- **Agent type**: `rudder-implement`
|
|
493
|
-
- **Task description**: Implement
|
|
522
|
+
- **Task description**: Implement all requirements in prd.md, consulting materials under `{TASK_DIR}/research/`; continue until the complete change set is written and report implementation complete. Do not dispatch `rudder-check` or run the quality gate during this step.
|
|
494
523
|
- **Dispatch prompt guard**: The prompt MUST start with `Active task: <task path>`, then explicitly say the spawned agent is already `rudder-implement` and must implement directly without spawning another `rudder-implement` / `rudder-check`.
|
|
495
524
|
|
|
496
525
|
The Codex sub-agent definition auto-handles the context load requirement:
|
|
@@ -504,7 +533,7 @@ The Codex sub-agent definition auto-handles the context load requirement:
|
|
|
504
533
|
Spawn the implement sub-agent:
|
|
505
534
|
|
|
506
535
|
- **Agent type**: `rudder-implement`
|
|
507
|
-
- **Task description**: Implement
|
|
536
|
+
- **Task description**: Implement all requirements in prd.md, consulting materials under `{TASK_DIR}/research/`; continue until the complete change set is written and report implementation complete. Do not dispatch `rudder-check` or run the quality gate during this step.
|
|
508
537
|
- **Dispatch prompt guard**: Tell the spawned agent it is already the `rudder-implement` sub-agent and must implement directly, not spawn another `rudder-implement` / `rudder-check`.
|
|
509
538
|
|
|
510
539
|
The platform prelude auto-handles the context load requirement:
|
|
@@ -518,19 +547,28 @@ The platform prelude auto-handles the context load requirement:
|
|
|
518
547
|
1. Load the `rudder-before-dev` skill to read project guidelines
|
|
519
548
|
2. Read `{TASK_DIR}/prd.md` for requirements
|
|
520
549
|
3. Consult materials under `{TASK_DIR}/research/`
|
|
521
|
-
4. Implement the code per requirements
|
|
522
|
-
5.
|
|
550
|
+
4. Implement the complete code change per requirements
|
|
551
|
+
5. Report implementation complete; do not load `rudder-check` yet
|
|
523
552
|
|
|
524
553
|
[/codex-inline, Kilo, Antigravity, Windsurf]
|
|
525
554
|
|
|
526
|
-
#### 2.2
|
|
555
|
+
#### 2.2 Verify `[required · after implementation; repeat only after fixes]`
|
|
556
|
+
|
|
557
|
+
**Check/Verify boundary (mandatory):** `Check` is the review of the complete
|
|
558
|
+
diff; `Verify` is the execution of lint, type-check, tests, build, and business
|
|
559
|
+
acceptance commands. Do not dispatch or load `rudder-check` while
|
|
560
|
+
2.1 is still writing code. The implementer must finish the complete
|
|
561
|
+
requirement set first. Then run Check once over the full task diff, followed by
|
|
562
|
+
one Verify pass. If Check or Verify finds issues, fix them and rerun the
|
|
563
|
+
affected stage; do not alternate implementation and verification for individual
|
|
564
|
+
files or partial requirements.
|
|
527
565
|
|
|
528
566
|
[Claude Code, Cursor, OpenCode, codex-sub-agent, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid, Pi]
|
|
529
567
|
|
|
530
568
|
Spawn the check sub-agent:
|
|
531
569
|
|
|
532
570
|
- **Agent type**: `rudder-check`
|
|
533
|
-
- **Task description**: Review
|
|
571
|
+
- **Task description**: Review the complete implementation diff against spec and prd, then run the Verify commands (lint, type-check, tests, and build). Fix all findings directly. This is the first full Check + Verify pass for the task, not an incremental review.
|
|
534
572
|
- **Dispatch prompt guard**: Tell the spawned agent it is already the `rudder-check` sub-agent and must review/fix directly, not spawn another `rudder-check` / `rudder-implement`.
|
|
535
573
|
|
|
536
574
|
The check agent's job:
|
|
@@ -544,7 +582,7 @@ The check agent's job:
|
|
|
544
582
|
|
|
545
583
|
[codex-inline, Kilo, Antigravity, Windsurf]
|
|
546
584
|
|
|
547
|
-
|
|
585
|
+
Only after the complete implementation is written, load the `rudder-check` skill for the full Check + Verify pass:
|
|
548
586
|
- Spec compliance
|
|
549
587
|
- lint / type-check / tests
|
|
550
588
|
- Compile/build verification (detect project type, run `mvn compile` / `go build` / `cargo check`, fix errors up to 3 rounds)
|
|
@@ -33,6 +33,12 @@ export interface TaskJson {
|
|
|
33
33
|
relatedFiles: string[];
|
|
34
34
|
notes: string;
|
|
35
35
|
meta: Record<string, unknown>;
|
|
36
|
+
requirements?: {
|
|
37
|
+
status: string;
|
|
38
|
+
confirmed_by: string | null;
|
|
39
|
+
confirmed_at: string | null;
|
|
40
|
+
prd_hash: string | null;
|
|
41
|
+
};
|
|
36
42
|
}
|
|
37
43
|
/**
|
|
38
44
|
* Produce a fully-populated canonical-shape TaskJson.
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"task-json.d.ts","sourceRoot":"","sources":["../../src/utils/task-json.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,MAAM,WAAW,QAAQ;IACvB,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,EAAE,MAAM,CAAC;IACpB,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACxB,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,OAAO,EAAE,MAAM,GAAG,IAAI,CAAC;IACvB,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,EAAE,MAAM,CAAC;IAClB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,aAAa,EAAE,MAAM,GAAG,IAAI,CAAC;IAC7B,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;
|
|
1
|
+
{"version":3,"file":"task-json.d.ts","sourceRoot":"","sources":["../../src/utils/task-json.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAEH,MAAM,WAAW,QAAQ;IACvB,EAAE,EAAE,MAAM,CAAC;IACX,IAAI,EAAE,MAAM,CAAC;IACb,KAAK,EAAE,MAAM,CAAC;IACd,WAAW,EAAE,MAAM,CAAC;IACpB,MAAM,EAAE,MAAM,CAAC;IACf,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;IACxB,KAAK,EAAE,MAAM,GAAG,IAAI,CAAC;IACrB,OAAO,EAAE,MAAM,GAAG,IAAI,CAAC;IACvB,QAAQ,EAAE,MAAM,CAAC;IACjB,OAAO,EAAE,MAAM,CAAC;IAChB,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,EAAE,MAAM,CAAC;IAClB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,aAAa,EAAE,MAAM,GAAG,IAAI,CAAC;IAC7B,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,QAAQ,EAAE,MAAM,EAAE,CAAC;IACnB,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC;IACtB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAC9B,YAAY,CAAC,EAAE;QACb,MAAM,EAAE,MAAM,CAAC;QACf,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;QAC5B,YAAY,EAAE,MAAM,GAAG,IAAI,CAAC;QAC5B,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;KACzB,CAAC;CACH;AAED;;;;;;;GAOG;AACH,wBAAgB,aAAa,CAAC,SAAS,GAAE,OAAO,CAAC,QAAQ,CAAM,GAAG,QAAQ,CAmCzE"}
|
package/dist/utils/task-json.js
CHANGED
|
@@ -43,6 +43,12 @@ export function emptyTaskJson(overrides = {}) {
|
|
|
43
43
|
relatedFiles: [],
|
|
44
44
|
notes: "",
|
|
45
45
|
meta: {},
|
|
46
|
+
requirements: {
|
|
47
|
+
status: "pending",
|
|
48
|
+
confirmed_by: null,
|
|
49
|
+
confirmed_at: null,
|
|
50
|
+
prd_hash: null,
|
|
51
|
+
},
|
|
46
52
|
};
|
|
47
53
|
return { ...base, ...overrides };
|
|
48
54
|
}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"task-json.js","sourceRoot":"","sources":["../../src/utils/task-json.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;
|
|
1
|
+
{"version":3,"file":"task-json.js","sourceRoot":"","sources":["../../src/utils/task-json.ts"],"names":[],"mappings":"AAAA;;;;;;;;;GASG;AAmCH;;;;;;;GAOG;AACH,MAAM,UAAU,aAAa,CAAC,YAA+B,EAAE;IAC7D,MAAM,KAAK,GAAG,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,CAAC;IACrD,MAAM,IAAI,GAAa;QACrB,EAAE,EAAE,EAAE;QACN,IAAI,EAAE,EAAE;QACR,KAAK,EAAE,EAAE;QACT,WAAW,EAAE,EAAE;QACf,MAAM,EAAE,UAAU;QAClB,QAAQ,EAAE,IAAI;QACd,KAAK,EAAE,IAAI;QACX,OAAO,EAAE,IAAI;QACb,QAAQ,EAAE,IAAI;QACd,OAAO,EAAE,EAAE;QACX,QAAQ,EAAE,EAAE;QACZ,SAAS,EAAE,KAAK;QAChB,WAAW,EAAE,IAAI;QACjB,MAAM,EAAE,IAAI;QACZ,WAAW,EAAE,IAAI;QACjB,aAAa,EAAE,IAAI;QACnB,MAAM,EAAE,IAAI;QACZ,MAAM,EAAE,IAAI;QACZ,QAAQ,EAAE,EAAE;QACZ,QAAQ,EAAE,EAAE;QACZ,MAAM,EAAE,IAAI;QACZ,YAAY,EAAE,EAAE;QAChB,KAAK,EAAE,EAAE;QACT,IAAI,EAAE,EAAE;QACR,YAAY,EAAE;YACZ,MAAM,EAAE,SAAS;YACjB,YAAY,EAAE,IAAI;YAClB,YAAY,EAAE,IAAI;YAClB,QAAQ,EAAE,IAAI;SACf;KACF,CAAC;IACF,OAAO,EAAE,GAAG,IAAI,EAAE,GAAG,SAAS,EAAE,CAAC;AACnC,CAAC"}
|