Files

FallenSigh 8fdf944555 feat: init mlkem project with Verilator test framework

- sync_rtl/common/: skid_buffer, pipeline_reg, defines (valid/ready)
- sync_rtl/mod_add/: modular adder example with Verilator C++ TB
- test_framework/: Python-driven Verilator compile/sim/compare pipeline
- test_framework/modules/mod_add/: 50-vector test plan, full鏈路 PASS
- .trellis/spec/: RTL and test_framework conventions documented

2026-06-24 19:43:29 +08:00

1.9 KiB

Raw Blame History

Continue Current Task

Resume work on the current task — pick up at the right phase/step in .trellis/workflow.md.

Step 1: Load Current Context

python3 ./.trellis/scripts/get_context.py

Confirms: current task, git state, recent commits.

Step 2: Load the Phase Index

python3 ./.trellis/scripts/get_context.py --mode phase

Shows the Phase Index (Plan / Execute / Finish) with routing + skill mapping.

Step 3: Decide Where You Are

get_context.py shows the active task's status field. Route by status + artifact presence:

status=planning + no prd.md → 1.1 (load trellis-brainstorm)
status=planning + prd.md exists + implement.jsonl not curated (only the seed _example row) → 1.3
status=planning + prd.md + curated implement.jsonl → 1.4 (run task.py start to enter Phase 2)
status=in_progress + implementation not started → 2.1
status=in_progress + implementation done, not yet checked → 2.2
status=in_progress + check passed → 3.1
status=completed (rare; usually archived immediately) → archive flow

Phase rules (full detail in .trellis/workflow.md):

Run steps in order within a phase — [required] steps must not be skipped
[once] steps are already done if the output exists (e.g., prd.md for 1.1; implement.jsonl with curated entries for 1.3) — skip them
You may go back to an earlier phase if discoveries require it

Step 4: Load the Specific Step

Once you know which step to resume at:

python3 ./.trellis/scripts/get_context.py --mode phase --step <X.X> --platform opencode

Follow the loaded instructions. After each [required] step completes, move to the next.

Reference

Full workflow, skill routing table, and the DO-NOT-skip table live in .trellis/workflow.md. This command is only an entry point — the canonical guidance is there.

1.9 KiB Raw Blame History