Skip to main content

​
Appendix D: JSONL Configuration Format Reference

​
File Entry

{"file": ".trellis/spec/backend/index.md", "reason": "Backend development guide"}

​
Directory Entry

{"file": "src/services/", "type": "directory", "reason": "Existing service patterns"}

​
Complete Example (fullstack implement.jsonl)

{"file": ".trellis/workflow.md", "reason": "Project workflow and conventions"}
{"file": ".trellis/spec/shared/index.md", "reason": "Shared coding standards"}
{"file": ".trellis/spec/backend/index.md", "reason": "Backend development guide"}
{"file": ".trellis/spec/backend/api-module.md", "reason": "API module conventions"}
{"file": ".trellis/spec/backend/quality.md", "reason": "Code quality requirements"}
{"file": ".trellis/spec/frontend/index.md", "reason": "Frontend development guide"}
{"file": ".trellis/spec/frontend/components.md", "reason": "Component conventions"}

​
Completion Marker Generation Rules

reason field → UPPERCASE + spaces replaced with underscores + _FINISH suffix:
reasonGenerated Marker
”TypeCheck”TYPECHECK_FINISH
”Lint”LINT_FINISH
”Code quality requirements”CODE_QUALITY_REQUIREMENTS_FINISH
”Finish work checklist”FINISH_WORK_CHECKLIST_FINISH