new-task

Purpose

• •Create one new task document under design/tasks.

Steps

1. •Decide file path

• •Standard paths:
  • •design/tasks/YYYY/MM/DD/YYYYMMDDa-short-slug.md (English)
  • •design/tasks/YYYY/MM/DD/YYYYMMDDa-short-slug.ja.md (Japanese)
• •Default language is Japanese.
• •Follow the user’s instructions if they specify path, date, language, or slug.

1. •Draft the document

• •Use GUIDE.md for English tasks or GUIDE.ja.md for Japanese tasks.
• •Follow the schema and template defined in the applicable guide.
• •Refer to existing task files for style and granularity.

1. •Apply front-matter rules

• •Set id as the task doc-id and keep it unique across the entire repository.
• •Keep id aligned with the filename stem.
• •Set adrs as a string array of related ADR doc-ids (use [] when none yet).
• •Keep plans as a string array of related plan doc-ids when applicable.

1. •Apply references rules

• •Keep a markdown reference list at the end of the file.
• •For links to markdown documents that define front-matter id:, use that doc-id as the reference label (no .md / .ja.md in labels).
• •Use label-style references in the body (for example, [K4x-ADR-014]).

1. •Finalize

• •Run make gen-index after creating the file to refresh task indexes.