notion-ticket

Request a new task page and the Skill first runs a duplicate check against the last 30 entries, then creates the page with a fixed skeleton: one section defining the task and why it is non-trivial, plus a contracts section with labeled bullet lines for paths, timing, and authorization.

Ask to organize the page and the Skill fetches it with comments, classifies each block as durable contract or transient note, and moves transient content into sub-pages rather than deleting it. It re-fetches right before writing to avoid overwriting concurrent edits.

The body holds only the task definition and facts still valid after completion, such as contracts, adopted and rejected design options, and code coordinates. MR lists, deployment order, checklists, measurements, and daily progress go into sub-pages like "작업 메모 — MR·배포·검증".

Yes, but only the contract layer is extracted from the Obsidian note; measurements and verification records stay in the note, which remains the source of truth. Wiki-style links are converted to Notion links or sub-pages since Notion does not render them.

The Skill never writes unverified contract lines, never deletes body content outright, and never replies to or resolves Notion comments without user confirmation. It also avoids code blocks with aligned spacing, excessive tables, and empty template sections.