2 +description: Run the ISP technology-review workflow from evidence to team decision
4 +argument-hint: "<
technology> [target-project or question]"
7 +#
Run a technology review 9 +**Technology and context**:
12 +Use the `twg`, `twg-confluence`, `twg-jira`, and `speak-as-oliver` skills.
13 +Confluence is the process authority; read current source pages instead of relying
14 +on remembered policy.
16 +##
Establish the review 18 +1. Read the current `Tech Reviews` process page in the RD space, its review
19 + template, and the linked Open Source/COTS clearing and Developer Weekly
21 +2. Find the Jira ticket carrying the `tech-review` label, or report that it is
22 + missing. Never create or mutate Jira state without explicit authorization.
23 +3. State the concrete goal: which decision this review enables, for whom, and
24 + in which target project.
25 +4. Identify the prototype or real product trial. Existing hands-on use counts;
26 + unsupported expectations do not. If no trial exists, stop at a bounded trial
27 + plan rather than writing a recommendation.
31 +- Prefer official documentation, primary repositories, current project code,
32 + generated reports, and observed trial results.
33 +- Separate facts, trial observations, unresolved questions, and judgments.
34 +- Name exact artifacts and boundaries. Do not collapse an input payload,
35 + persisted event, report format, protocol, or API into vague terms such as
37 +- Check the technology and every required component against the current license
38 + matrix. A whitelist result is cleared; a blacklist result blocks adoption;
39 + anything else requires the documented clearing process.
40 +- Evaluate the dimensions required by the current Techreview template, including
41 + functionality, performance, usability, compatibility, security,
42 + community/support, licensing/cost, and recommendation.
46 +- Use the current template, but keep the result terse and decision-oriented.
47 +- Write in the language and register of the target space; for Oliver-authored
48 + German text, apply `speak-as-oliver` and natural technical German.
49 +- Explain practical findings through concrete examples from the trial.
50 +- Make the recommendation bounded: target project, initial scope, workflow,
51 + unresolved gates, and conditions for wider adoption.
52 +- Leave the final accept/reject decision to the team.
54 +Present the complete draft and its evidence links before any Confluence write.
55 +Apply feedback narrowly. Wait for explicit authorization before publishing.
57 +##
Complete after approval 59 +1. Create or update the Tech Review under the canonical parent using the
60 + current content type and template conventions.
61 +2. Read it back and verify title, body, links, status, and parent.
62 +3. Create the required Developer Weekly announcement in Oliver's voice, link
63 + the review, and add the `weekly` label.
64 +4. Read back the announcement and verify its link and label.
65 +5. Report direct URLs, remaining questions, and the team decision still needed.
67 +Never claim a trial, license clearance, publication, label, or decision before