Atlassian Templates
Atlassian Templates: Make project work visible and actionable. Review the backlog, owners, dependencies, dates, and current status and produce a delivery view with owners and next checkpoints.
--- name: project-management-atlassian-templates description: Use for atlassian templates when asked to make project work visible and actionable; produce a delivery view with owners and next checkpoints. license: MIT metadata: author: Thrive category: project-management --- # Atlassian Templates ## When to use Use this skill for atlassian templates when you need to make project work visible and actionable. The expected result is a delivery view with owners and next checkpoints. ## Boundaries Work within the requested task and its stated acceptance criteria. Drafting an artifact does not authorize publishing it, spending funds, changing a live system, or contacting another person. Identify any such action separately before taking it. ## Inputs Inspect the backlog, owners, dependencies, dates, and current status. Resolve missing information that would change the method; state lesser assumptions in the result. ## Method 1. **Diagnose.** Map the deliverable to tasks, owners, dependencies, dates, and the evidence required to call each task done. 2. **Decide.** Connect work items to a milestone and escalation path. 3. **Produce.** Build a delivery view with owners and next checkpoints from the inspected material; keep assumptions distinguishable from observed facts. ## Decision rules - Identify the critical path and escalation point. Split ambiguous work before assigning it or promising a date. - When sources or constraints conflict, record the conflict and choose the path supported by the user's goal and the strongest available evidence. If neither path can be supported, identify the missing decision before changing the artifact. ## Domain rules - Assign milestones and dependencies to named owners with dates. - Define how a blocker is escalated and when schedule status will be reviewed. ## Verification Check that status reflects actual evidence rather than tool labels. Compare the result with the user's acceptance criteria and record any unverified boundary. Provide a plan or status record with blocked items, decisions needed, next milestone, and a review cadence. ## Stop conditions If a material input, required authorization, or a safe way to verify the result is absent, stop the affected action. Return the specific blocker and the smallest fact or decision needed to continue. Do not report an unrun check as passed. ## Output Provide a delivery view with owners and next checkpoints. Include the decisive evidence and actual verification result. Name any artifact location and unresolved issue that affects its use. <!-- MIT License Copyright (c) 2026 Thrive Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->