ContentQ Weekly Plan

🔨 ACTION REQUIRED: Break down frontend tickets into granular sub-tasks

Tickets requiring breakdown:
• ENG-496: Content Studio Views (Canvas/Board/Calendar)
• ENG-497: HITL Screens (3 for Happy Path: Brief/Draft/Final Review)
• ENG-498: Frontend-Backend Integration
• ENG-500: CAPSTONE — Blog from Scratch E2E Integration

What Ashish needs to do:
1. Break each ticket into specific, estimable sub-tasks
2. Add time estimates to each sub-task
3. Identify dependencies between sub-tasks
4. Flag any blockers or questions early

Output: Updated Linear tickets with sub-issues, or a breakdown document

Backend Work Blocks:

Block 1: Core Handoff & Tool Infrastructure (~2 days)
Enables agents to delegate work and execute tools within the LLM loop, forming the foundation for Oscar's prompt-based orchestration.
Components: Private mode handoffs with parent lineage, tool executor node, LLM loop with on-demand handoff/timeline loading, workflow runner migration.

Block 2: Global Tools & Orchestration Framework (~5-10 days, partial this sprint)
Provides the tool ecosystem Oscar needs to dynamically invoke subworkflows, manage state, and coordinate agent sequences with HITL gates.
Components: Subworkflow execution tools, handoff/timeline tools, sequence block orchestration, HITL integration loops.

Block 3: Agent Development Framework (~1-2 days)
Delivers a repeatable process for building and testing agents, validated by shipping the first end-to-end agent with Anish and Gaurav.
⚠️ Blocked on Block 1 completion.

Block 4: Frontend API Contract (~1-2 days)
Defines the API surface for frontend integration, enabling parallel UI development against stable backend interfaces.
⚠️ Blocked on Block 1 + partial Block 2.

---

Tickets:
• ENG-486: Oscar Orchestration + Handoffs
• ENG-487: Marketing Brain ⚠️ OUT OF SCOPE
• ENG-488: API Contracts for Frontend (2 tranches)

To Confirm Monday:
• Block 1 completion status — what's done vs. remaining?
• Oscar minimum scope — what's minimal for capstone?
• API modifications scope — existing endpoints vs. net-new?

Agent requirements for Blog from Scratch capstone workflow.

Output: Initial version covering the capstone workflow agents (Oscar, Researcher, Strategist, Writer, Quality Auditor)

User onboarding flow UI/UX feature spike.

🤝 Collaborative: Anish and Gaurav working together

Output: Feature spike (not full implementation)

Assistant Panel requirements + wireframes spike.

🤝 Collaborative: Anish and Gaurav working together

Priority spike for the week.

Content Studio Views implementation: Canvas, Board, Calendar.

⚠️ NEEDS BREAKDOWN: Break into sub-tasks with estimates before starting. See ENG-501.

Due: Progressive through week
Dependency: Share latest frontend architecture doc (plus plan docs) with Anish (Monday)

Architecture: Oscar uses prompt-based orchestration:
Intent classification → Dynamic plan generation → Agent delegation → HITL coordination

✅ Capstone Scope:
• Prompt-based intent classification
• Dynamic plan generation for Blog from Scratch flow
• Handoff passing between agents
• HITL gate coordination (3 gates)
• Delegation to middle-layer agents

❌ Out of Scope This Week:
• Full multi-intent support
• Budget tracking
• Skills registry integration

Part of: Block 1 (Core Handoff) + Block 2 (Orchestration Framework)

E2E requirements for Content Studio Workflow V1.

Includes:
• API contracts/schemas
• HITL response formats
• Button configurations
• Template data structures
• Error/loading states for Ashish

Test workflow on Claude Code sandbox and refine prompts.

🤝 Collaborative: Anish and Gaurav working together on Claude Code sandbox

Output: Tested and improved prompts for all agents in Blog from Scratch workflow

Granular frontend planning and documentation.

Output: Visibility into frontend work breakdown

Comprehensive agent requirements covering ~90% of all product workflows.

Output: Detailed documentation shared with Raunak for backend implementation

Internal tool spec for agent/workflow building (Super User product).

Output: Requirements document for internal builder tool

Checklist of what's blocking test-ready state for ContentQ.

Output: Punch list document

API contracts for frontend integration — delivered in 2 tranches:

📄 Tranche 1: Capstone APIs (Wed Dec 11)
APIs for capstone scope — limited but functional
• Endpoints needed for Blog from Scratch E2E
• Minimum viable surface for 3 HITL gates
• Focus on happy path

⚙️ Tranche 2: Full V1 Architecture (Thu Dec 12)
Full V1 API architecture
• Complete endpoint coverage
• Error handling
• Edge cases

Blocked on: Block 1 + partial Block 2 completion

Content Studio templates.

Due: Tuesday AM (if not completed Monday)

Test different architecture approaches in Claude Code sandbox and finalize architecture for Content Studio workflow.

🤝 Collaborative: Anish and Gaurav working together on Claude Code sandbox

Output: Finalized architecture, initial plan shared with Raunak for review

Implementation specs handoff to Ashish for frontend integration.

Output: Clear specs for Ashish to implement frontend integration

3 HITL Screens for Happy Path:

1. Brief Review
Content: Title, outline, key points, strategic angle
Actions: Approve / Modify / Regenerate

2. Draft Review
Content: Full draft with citations
Actions: Approve / Edit / Reject

3. Final Review
Content: SEO-optimized content
Actions: Approve / Publish / Revise

Note: QC handled by sub-agents (ContentQCAgent within ContentStudioAgent)

Frontend connected to Oscar orchestration backend.

⚠️ NEEDS BREAKDOWN: Break into sub-tasks with estimates before starting. See ENG-501.

Dependencies:
• API design documentation from Raunak (Wed)
• Actual APIs ready from Raunak (could slip to Thu night)
• Implementation specs from Gaurav (Friday)

CAPSTONE GOAL

⚠️ NEEDS BREAKDOWN: Break into sub-tasks with estimates before starting. See ENG-501.

Blog from Scratch runs end-to-end:
• User input → Oscar → agents → 3 HITL gates → scored draft output
• Frontend connected to backend orchestration
• All 3 HITL gates functional
• Multi-attribute scoring displays

Dependencies: All P1 items complete

⚠️ OUT OF SCOPE THIS WEEK

Reason: Using adhoc customer documents for context injection instead of full Marketing Brain implementation.

Revisit: Next sprint after capstone is validated