Add workflow-first marketing skills and tooling for Reply.cash agents

[potlock-support]

Summary

Agents supporting Reply.cash marketing need better workflow support, not just more generic tools.

Right now, agents can do pieces of the job, but the full workflow is still fragmented. The result is inconsistent execution across research, messaging, content creation, review, and issue tracking.

Problem

The current environment does not fully support the actual workflow a marketing agent needs to follow for Reply.cash.

A typical task looks like:

1. read brand context
2. fetch current product/docs context
3. research competitors or market narratives
4. draft messaging or content
5. validate against compliance/brand constraints
6. turn gaps into trackable issues or follow-up tasks

Today, this flow is too brittle. Agents may run into:

• missing skills for end-to-end marketing work
• weak handoffs between brand context and writing tasks
• inconsistent research workflows
• unclear review/checklist steps before publishing
• issue creation workflows that are disconnected from the marketing process

Why this matters

Reply.cash marketing depends on consistency.

Agents need to reliably move from:
context → research → strategy → draft → review → execution

If the workflow is incomplete, output quality drops:

• more avoidable follow-up questions
• weaker positioning
• inconsistent copy
• missed compliance or brand constraints
• less reusable work across sessions

Requested improvement

Create a workflow-first marketing capability for agents working on Reply.cash.

This should support:

1. Brand-first workflow

• always start from the relevant BRAND-*.md file
• reuse stored positioning, personas, objections, and messaging
• make brand context easy to retrieve and update

2. Research workflow

• fetch current product facts and docs
• research adjacent competitors and market narratives
• structure findings so they can feed directly into messaging work

3. Content workflow

• generate copy from brand + research inputs
• support common outputs like posts, threads, landing page copy, campaign concepts, and messaging angles
• keep outputs aligned with Reply.cash positioning and compliance constraints

4. Review workflow

• check drafts against brand rules
• check for prohibited framing or inaccurate claims
• provide a lightweight QA checklist before publishing or sharing

5. Issue-tracking workflow

• convert identified gaps into GitHub issues cleanly
• make follow-up work part of the workflow, not a separate ad hoc step

Acceptance criteria

• Agents can complete a full Reply.cash marketing workflow without major capability gaps
• Brand context is consistently used at the start of marketing tasks
• Research outputs feed cleanly into content generation
• Drafts can be reviewed against brand/compliance rules before use
• Workflow gaps can be turned into GitHub issues without friction

Context

This issue comes from real usage where agents were able to do parts of marketing work, but not the full workflow smoothly enough for reliable execution.