Skip to main content
addly

Testable configurations, never screenshots to imitate.

Each recipe starts from a fictional scenario, provides a copyable configuration, and opens a quick start that names its initial preset, actions, and expected outputs. It prepares a test; it does not announce a published feature.

Four initial recipes

Release criteria, portfolio health, actionable minutes, and page-to-project context.

Jira · Issue panel

RECIPE 01

Release review — Readiness for Jira

Open the documented preset in the lab, verify its outputs, then copy the configuration into your protocol.

Open the guided recipe

App configuration — Readiness for Jira

RECIPE — RELEASE REVIEW

Surface: Jira · Issue panel
Mode: preview in a test project

CRITERIA
- Specification reviewed: required
- Success measure defined: required
- Rollback documented: blocking

VERDICT
- Ready: all blocking criteria are verified
- In review: at least one criterion remains open

TEST IN THE DEMO
- clear and restore a criterion;
- hide and show details;
- inspect the verdict source.

EVIDENCE STILL BLOCKED
- empty state;
- insufficient permission;
- recoverable error.

Jira · Project page

RECIPE 02

Portfolio health — Portfolio Insights

Open the documented preset in the lab, verify its outputs, then copy the configuration into your protocol.

Open the guided recipe

App configuration — Portfolio Insights

RECIPE — PORTFOLIO HEALTH

Surface: Jira · Project page
Scope: three fictional initiatives

INDICATORS
- moved deadline;
- blocking dependency;
- pending decision;
- capacity below the defined threshold.

OUTPUT
- explained state;
- accessible source indicator;
- decision owner;
- next review.

Confluence · Content macro

RECIPE 03

Actionable minutes — Page Summary

Open the documented preset in the lab, verify its outputs, then copy the configuration into your protocol.

Open the guided recipe

App configuration — Page Summary

RECIPE — ACTIONABLE MINUTES

Surface: Confluence · Content macro
Data: fictional page only

SECTIONS
- Recorded decisions
- Open questions
- Actions, owners, and due dates
- Sources in the page

RULES
- no decision without a source passage;
- no action without an owner;
- human validation before publication.

Confluence · Context panel

RECIPE 04

Page-to-project context — Context Linker

Open the documented preset in the lab, verify its outputs, then copy the configuration into your protocol.

Open the guided recipe

App configuration — Context Linker

RECIPE — LINK CONTEXT

Surface: Confluence · Context panel
Mode: suggestion, then confirmation

LINK TYPES
- project;
- issue;
- decision;
- document.

GUARDRAILS
- respect host permissions;
- display the link reason;
- create nothing without confirmation;
- allow relationship deletion.

A recipe deserves verification.

  • 01Name fictional data and test scope.
  • 02State prerequisites and minimum permission.
  • 03Describe initial state, action, and expected output.
  • 04Exercise an exposed limitation or record it as blocked evidence.
  • 05Version configuration with documentation.
  • 06Make deletion or rollback explicit, or mark it absent.

Copy fewer settings. Copy more context.

A good recipe preserves the scenario, guardrails, and verification with the configuration.