brainstorm-promotion: author agents/skills/partnerships.md

[reubenr0d]

brainstorm-promotion: blocker for the partnership-tracker brainstorm agent in COMPANY.md.

Background

partnership-tracker is the only consumer of this skill (1:1 mapping). It needs to understand the partner-file frontmatter schema, the 0xLabs intros pipeline, and the chain deployment lifecycle so it can detect stale next_milestone_date rows, draft follow-ups for awaiting_response partners, and surface live blockers without inventing schema.

Spec (lifted from COMPANY.md L171-176)

- name: partnerships
  proposedPath: agents/skills/partnerships.md
  description: >
    Partner file frontmatter (status, counterpart, next_milestone,
    co_marketing, funding_intros), 0xLabs intros pipeline, chain
    deployment lifecycle. Needed by partnership-tracker.

Acceptance criteria

• New agents/skills/partnerships.md matching the file conventions of the 4 existing skill files under agents/skills/.
• Documents the canonical partner-file frontmatter schema by reading the 5 active per-partner files under growth/partnerships/ (don't invent fields — extract empirically). Required fields: status, counterpart, next_milestone, next_milestone_date, co_marketing, funding_intros.
• Documents the status enum (awaiting_response, responded, declined, active, etc. — extract from growth/partnerships/README.md legend).
• Documents the co_marketing and funding_intros enums (with definitions from the legends in growth/partnerships/README.md).
• Documents the 0xLabs intros pipeline structure (110-row table per growth/partnerships/README.md §0xLabs introductions) including the awaiting_response → responded → graduate to All partners workflow.
• Documents the chain deployment lifecycle (cross-references growth/partnerships/chains/README.md and the per-chain files).
• Defines the rules partnership-tracker should enforce: how stale is too stale for next_milestone_date, when to file a blocker issue vs surface a soft ticket, etc.
• CHANGELOG.md entry timestamped per repo convention.

Lifecycle next steps after PR merges

1. Reference the skill from the partnership-tracker agent prompt file (separate issue).
2. Once partnership-tracker flips state: brainstorm → state: active, also flip skills.proposed → skills.active for partnerships.

References

• COMPANY.md §Skills L171-176 (canonical spec)
• Consumer: COMPANY.md §Brainstorm partnership-tracker.proposedSkills (L383)
• Source material: growth/partnerships/, growth/partnerships/README.md, growth/partnerships/chains/README.md, growth/partnerships/_TEMPLATE.md (if exists)
• Existing skill conventions: agents/skills/vault-manager.md, agents/skills/atlas-quality.md

[reubenr0d]

Implemented: agents/skills/partnerships.md — frontmatter schema, blocker taxonomy, and dedupe heuristics for partnership-tracker.