Project template

Project templates aren't a first-class feature yet — there's no "save this project's issue tree as a template and instantiate four times a year" button today. The closest building blocks Paperclip already gives you are Routines and the issue parent/child hierarchy, and you can combine them to get most of what you're after.

A pattern that works well for a recurring project like a quarterly cycle:

One quarterly Routine that seeds the parent issue. Schedule trigger on a cron like 0 9 1 1,4,7,10 (1st of Jan/Apr/Jul/Oct at 09:00). Title and instructions describe the cycle — "Q{{quarter}} cycle kickoff" using a {{quarter}} variable. When it fires, you get a fresh parent issue under the same project, automatically. Sub-issues for each step. Either: have the assignee agent decompose the parent issue on first run (the heartbeat protocol explicitly supports creating subtasks via POST /api/companies/{companyId}/issues with parentId set), or chain a small set of Routines that each create one of the standard sub-issues with blockedByIssueIds linking them in the right order. Blocker completion sends wakeups to the next dependent issue, which is how you enforce "in the correct order." Reuse the same Project across cycles — you keep the workspace, env vars, repo binding, and budget. The Project's Issues tab gives you a per-cycle view by parent issue.

For bigger templates (dozens of subtasks), keep the canonical structure as a Markdown checklist in the routine's instructions and let the agent expand it into real parentId-linked subtasks at run time. That's lightweight, lives entirely in product, and survives schema changes better than a hand-rolled clone script.

A "duplicate project / issue tree" feature is a reasonable idea — this Ideas thread is the right place for it. If you'd like, sketch the minimum behaviour you'd want (clone issues only? include sub-issues? include linked goals? reset statuses?) and we can refine it.