This epic contains spikes that track planning effort for Assisted Installer by writers only. (It should not be used to track planning by content strategists or other associates)

Create a spike only when a writer is to start planning to avoid unnecessary tickets in case a content strategist plans the epic/story instead.

Linked is a Confluence page with a list of affected epics grouped by (planning and writing) priority.

When creating a spike:

• Clone TELCODOCS-1372
• Set Component to correspond to the docs:* label on the epic
• Assign the spike and add it to the sprint it it will be worked on
• Add the "is related to" link between the spike and the epic that is being planned
• Set the writer who is going to be assigned to the spike as Doc Contact in the affected epic