ContentTwin — AI social-media agent for small orgs

[don-petry]

Concept

ContentTwin — "AI-powered Social Media Agent for small organizations — enterprise-quality social presence at non-profit pricing" (per the source repo's own description). The intended product is an AI agent that plans, drafts, and publishes social-media content on a regular cadence for small orgs and non-profits that can't afford a dedicated social/marketing person or an agency.

Current state / maturity

Ideation-stage. The repo (petry-projects/ContentTwin, created 2026-03-26) currently contains only org-standard scaffolding — CI, reusable-workflow caller stubs, rulesets, LICENSE/SECURITY, agent-guideline pointers. There is no product code, no README, no PRD, and 0 Discussions. Notable grounding signals:

• The product concept exists only as the GitHub repo description — there is no spec or design doc backing it.
• .github/copilot-instructions.md mis-describes the repo as a "repository security/settings automation tool" (templated boilerplate that leaked from the org repo-template) — it does not reflect the social-media-agent concept.
• A daily "ContentTwin Audit — content pipeline issues" agent files issues referencing an empty queue/ content-pipeline directory — but no queue/ directory exists in the repo. The audited pipeline is aspirational/described, not built.
• The feature-ideation.yml workflow still carries the placeholder project_context (never customized to the product).

Why it's in the incubator

This is the first onboarding into the new pre-product incubator (a PILOT). ContentTwin is a real, named, still-in-ideation product concept with essentially nothing built yet — exactly the front-of-funnel stage the incubator is for. Tracking it here gives the concept a trackable ideation surface and a decision brief to hang a human go/no-go on.

ContentTwin's canonical home remains its own repo — this incubator entry is for ideation tracking only, not a move.

Source

• Source repo: https://github.com/petry-projects/ContentTwin
• Decision brief (in PR): ideas/content-twin/brief.md

---

Decision brief: the PRD-lite / decision brief for this idea is in #7 (ideas/content-twin/). That PR is the go/no-go artifact; this Discussion is the tracking surface.