Starting a New Project
Type /deevoted-start
Type the command in any Slack channel where the pipeline is active.
Answer intake questions
Project Coordinator asks about the client, project type, scope, and specific requirements. These answers shape which skills are assigned.
Wait for confirmation
Coordinator creates the Google Drive folder structure, identifies which skills the project needs, and assembles the team.
First assignment notification
Typically, the Strategist is assigned first. You'll see a notification in your project channel confirming the assignment.
First deliverable arrives
When the Strategist finishes the Project Brief, you'll get a notification with Approve, With Client, Request Revisions, and Discuss in Claude buttons.
Reviewing and Approving
When a deliverable is ready, you'll see a notification in Slack with a link to the file in Google Drive.
Open the Google Doc version for review — it supports comments and tracked changes.
Look for: accuracy, completeness, and quality.
Click Approve when satisfied. The pipeline advances — the deliverable is handed off to the next skill.
Click Request Revisions when something needs to change. Add revision notes describing the specific changes — the deliverable regenerates with your feedback applied.
Writing Effective Revision Requests
The quality of your revision feedback directly affects the quality of the revision.
Be specific: "The hero headline should lead with the outcome, not the feature" is actionable. "I don't like the headline" is not.
Reference the deliverable: "In section 3 of the project brief, the audience description should include..." gives a clear location.
Distinguish must-fix from nice-to-have: If some issues are critical and others are suggestions, say so.
Each deliverable gets up to three revision cycles by default. After three rounds, the Coordinator escalates.
Checking Status
If /deevoted-pending returns nothing, you're all caught up.