Skip to main content

write-what-the-two-sides-agree-on

Ends the exploration with a joint thesis one page long that both companies would recognize, and says what our own side has to get out of any arrangement, which the shaping that follows works from. Use it when running `ref/prt/explore-an-alliance` and `ref/prt/structure-an-alliance`.

Ir a la instalación

Datos de origen

Repositorio
jeffrschneider/agentcatalog
Última actividad en el origen
22 de agosto de 2026 a las 14:12
Idioma detectado de SKILL.md
inglés
Estrellas
0
Forks
0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
write-what-the-two-sides-agree-on
description
Ends the exploration with a joint thesis one page long that both companies would recognize, and says what our own side has to get out of any arrangement, which the shaping that follows works from. Use it when running `ref/prt/explore-an-alliance` and `ref/prt/structure-an-alliance`.
license
CC-BY-4.0
metadata
{"agent":"alliance-scout","agent-version":"1"}
# Write what the two sides agree on ## What it does Ends the exploration with a joint thesis one page long that both companies would recognize, and says what our own side has to get out of any arrangement, which the shaping that follows works from. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Set What Each Side Must Get** - `ref/prt/structure-an-alliance`, activity 2 - [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md) - **Write the Joint Thesis** - `ref/prt/explore-an-alliance`, activity 13 - [Explore an Alliance](../../../../processes/partners/explore-an-alliance.md) ## What to record The strategic reason as written before any company was named, dated. The build, buy or ally comparison and what it concluded. The candidate list with the source of each name. Per candidate: what they sell and to whom, the fit score, the criteria it was scored on, and the inputs behind it. The shortlist with the order of approach and who was to make it. Per candidate approached: the date, the person who made contact, and the mutual confidentiality agreement signed before anything beyond public material was shown. The numbers each side traded and the agreement they were traded under. The joint thesis at a version. The exploration record, kept either way, readable by the next run that names the same candidate. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.
Ver en GitHub