Dev Day Autopilot — Implementation Plan

# Dev Day Autopilot — Implementation Plan

## For: Automate Me If You Can Hackathon (WeMakeDevs × Accomplish)
## Deadline: February 22, 2026

---

## Project Summary

**Dev Day Autopilot** is an Accomplish automation that runs every morning and organizes your entire developer life in under 2 minutes. It chains together **all 4 Accomplish capabilities** (file management, browser automation, document creation, custom skills) into one seamless workflow.

**One prompt → organized Downloads, GitHub activity summary, trending dev articles, and a daily briefing document.**

---

## Why This Wins (Judging Criteria Mapping)

| Criteria | How We Score |
|----------|-------------|
| **Real-World Impact** | Every developer has a messy Downloads folder and scattered info sources. This saves 30+ min daily. |
| **Creativity & Originality** | Nobody's done "morning autopilot for devs." Chains 4 different capabilities uniquely. |
| **Learning & Growth** | Shows learning journey: file ops → browser → docs → skills. Document the "aha" moments. |
| **Technical Execution** | Multi-step pipeline, error handling, real file manipulation, browser automation. |
| **Demo & Presentation** | INCREDIBLE before/after: chaotic desktop → organized briefing in 2 minutes. |
| **Best Use of Accomplish** | Uses ALL features: file management + browser automation + document creation + custom skills. |

---

## Architecture Overview

```
USER RUNS: "Run Dev Day Autopilot"
         │
         ▼
┌─────────────────────────────────────────────┐
│  PHASE 1: FILE MANAGEMENT                    │
│  (Accomplish File Operations)                │
│                                              │
│  1. Scan ~/Downloads folder                  │
│  2. Categorize files by type                 │
│  3. Move files into organized subfolders:    │
│     - Documents/ (pdf, doc, txt)             │
│     - Images/ (png, jpg, svg)                │
│     - Code/ (zip, tar, repos)               │
│     - Installers/ (dmg, exe, deb, AppImage)  │
│     - Archives/ (old files > 30 days)        │
│  4. Rename files with dates if needed        │
│  5. Generate file summary (what was moved)   │
└──────────────────┬──────────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────────┐
│  PHASE 2: BROWSER AUTOMATION                 │
│  (Accomplish Browser Control)                │
│                                              │
│  1. Open GitHub → check notifications        │
│  2. Visit user's GitHub profile → get        │
│     recent activity (PRs, issues, commits)   │
│  3. Open Hacker News → scrape top 5 posts    │
│  4. Open Dev.to → scrape trending articles   │
│  5. Collect all data for briefing            │
└──────────────────┬──────────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────────┐
│  PHASE 3: DOCUMENT CREATION                  │
│  (Accomplish Document Generation)            │
│                                              │
│  1. Generate "Daily Briefing" markdown doc   │
│  2. Sections:                                │
│     - 📁 File Organization Summary           │
│     - 🔔 GitHub Notifications & Activity     │
│     - 📰 Trending Dev News (HN + Dev.to)    │
│     - ✅ Suggested Tasks for Today           │
│     - 📊 Quick Stats                        │
│  3. Save to ~/Documents/DailyBriefings/     │
│     with date: briefing-2026-02-16.md        │
└──────────────────┬──────────────────────────┘
                   │
                   ▼
┌─────────────────────────────────────────────┐
│  PHASE 4: CUSTOM SKILL                       │
│  (Save as Reusable Accomplish Skill)         │
│                                              │
│  1. Save entire pipeline as                  │
│     "Dev Day Autopilot" skill                │
│  2. One-click run any morning                │
│  3. Configurable (choose which phases run)   │
└─────────────────────────────────────────────┘
```

---

## Detailed Implementation Tasks

### TASK 1: Project Setup & Test Data
**Assignee:** Any agent  
**Priority:** P0 (do first)  
**Time:** 30 min  

**What to do:**
1. Create this folder structure inside `/home/anurag/hack/accomplish/dev-day-autopilot/`:
```
dev-day-autopilot/
├── README.md                    # Project overview for hackathon judges
├── IMPLEMENTATION_PLAN.md       # This file
├── skill/
│   └── dev-day-autopilot.md     # The actual Accomplish skill prompt
├── test-data/
│   └── setup-test-downloads.sh  # Script to populate ~/Downloads with test files
├── sample-output/
│   └── briefing-2026-02-16.md   # Example of what the daily briefing looks like
└── demo/
    └── demo-script.md           # 3-minute video script
```

2. Create `test-data/setup-test-downloads.sh`:
   - Bash script that creates 15-20 dummy files in ~/Downloads to simulate a messy folder
   - File types: 3 PDFs, 3 images (png/jpg), 2 zip files, 2 .deb/.AppImage installers, 3 random text/code files, 2 old files (touch with old timestamps)
   - Give them realistic but messy names like `Screenshot 2026-02-10 at 3.45.12 PM.png`, `final_report_v3_FINAL(1).pdf`, `node-v20.11.0-linux-x64.tar.gz`
   - This is used to demonstrate the "before" state in the demo

3. Create `sample-output/briefing-2026-02-16.md`:
   - A realistic example of what the daily briefing output looks like
   - Include all sections: file summary, GitHub activity, trending articles, tasks
   - This helps judges understand the output format without running the automation

**Acceptance criteria:**
- [ ] Folder structure exists
- [ ] Test data script is executable and creates realistic messy Downloads
- [ ] Sample output shows a compelling daily briefing document
- [ ] No meta/planning files beyond this plan and README

---

### TASK 2: Write the Accomplish Skill Prompt
**Assignee:** Any agent  
**Priority:** P0 (do first, this IS the project)  
**Time:** 2 hours  
**File:** `skill/dev-day-autopilot.md`  

**What to do:**

Write the actual prompt/instruction that will be pasted into Accomplish as a Custom Skill. This is the CORE deliverable of the entire project.

**Important context about how Accomplish works:**
- Accomplish is a desktop AI agent (Electron app) that uses LLM providers (OpenAI, Anthropic, etc.)
- You interact with it by typing natural language prompts
- It has built-in capabilities: file system operations, browser automation (Playwright), document creation
- "Custom Skills" are saved prompts that can be reused — they're stored in a SQLite DB via SkillsManager
- When you create a skill, you give it a name and a prompt. The prompt tells the AI what to do.
- The AI agent then executes the prompt using its available tools (file ops, browser, etc.)
- Every action requires user approval before execution

**The skill prompt should instruct the AI agent to:**

**Phase 1 — File Organization:**
```
Scan the user's ~/Downloads directory. 
Categorize every file by type:
- Documents: .pdf, .doc, .docx, .txt, .md, .csv, .xlsx, .pptx
- Images: .png, .jpg, .jpeg, .gif, .svg, .webp
- Code: .zip, .tar.gz, .tar, .git, .py, .js, .ts, .json
- Installers: .dmg, .exe, .msi, .deb, .rpm, .AppImage
- Videos: .mp4, .mkv, .avi, .mov
- Other: anything else

Create these subfolders if they don't exist:
~/Downloads/Sorted-Documents/
~/Downloads/Sorted-Images/
~/Downloads/Sorted-Code/
~/Downloads/Sorted-Installers/
~/Downloads/Sorted-Videos/
~/Downloads/Sorted-Other/

Move each file to its category folder.
Files older than 30 days → move to ~/Downloads/Archive-[date]/
Keep a running list of what was moved where.
```

**Phase 2 — Browser Automation:**
```
Open a browser and perform these tasks:
1. Go to https://github.com/notifications — capture/summarize visible notifications
2. Go to https://news.ycombinator.com — extract the top 5 post titles + links + points
3. Go to https://dev.to — extract the top 5 trending article titles + links
Compile all findings.
```

**Phase 3 — Document Generation:**
```
Create a markdown document at ~/Documents/DailyBriefings/briefing-YYYY-MM-DD.md
with this structure:

# 🚀 Dev Day Briefing — [Date]

## 📁 File Organization Summary
[List what files were moved and where]
- X documents sorted
- X images sorted
- X code files sorted
- X files archived (older than 30 days)

## 🔔 GitHub Activity
[Notifications and recent activity from GitHub]

## 📰 Trending in Tech
### Hacker News Top 5
1. [Title](url) — X points
...

### Dev.to Trending
1. [Title](url)
...

## ✅ Suggested Tasks for Today
Based on your GitHub notifications and file activity:
1. [Generated suggestion]
2. [Generated suggestion]
3. [Generated suggestion]

## 📊 Quick Stats
- Files organized: X
- Files archived: X
- GitHub notifications: X
- Generated at: [timestamp]

---
*Generated by Dev Day Autopilot — Accomplish Custom Skill*
```

**Skill format:**
The file should contain:
- Skill Name: "Dev Day Autopilot"
- Skill Description: one-liner for display in Accomplish
- The full prompt (all 3 phases combined into one coherent instruction)
- Notes on how to install it (paste into Accomplish → Custom Skills → New Skill)

**Acceptance criteria:**
- [ ] Single coherent prompt that instructs the AI to execute all 3 phases
- [ ] Prompt is clear, specific, and actionable (no vague instructions)
- [ ] File includes installation instructions for Accomplish
- [ ] Prompt explicitly mentions user approval at each major step
- [ ] Output format is well-defined and structured

---

### TASK 3: Write the README
**Assignee:** Any agent  
**Priority:** P0  
**Time:** 1 hour  
**File:** `README.md`  

**What to do:**

Write a compelling README that makes judges want to give you the prize. This is what they'll read on your GitHub repo.

**Required sections (in this order):**

1. **Title & One-liner** 
   - "Dev Day Autopilot — Your Morning Routine, Automated"
   - One sentence: what it does

2. **The Problem (3-4 sentences)**
   - Developers start each day with: messy Downloads folder, unread GitHub notifications, no idea what's trending, no organized task list
   - This scattered start wastes 30+ minutes before you write a single line of code
   - Make it relatable and specific

3. **The Solution (3-4 sentences)**
   - One Accomplish automation that runs every morning
   - Organizes files, checks GitHub, grabs trending articles, generates a daily briefing
   - All in under 2 minutes, all on your local machine

4. **Demo** (placeholder for video embed)
   - `[▶️ Watch the 3-minute demo](link-to-video)`
   - Screenshots: before (messy) and after (organized)

5. **How It Works** (visual diagram)
   - Show the 4 phases with icons/emojis
   - Keep it simple: Input → Process → Output

6. **Accomplish Features Used**
   - Table showing which Accomplish features are used and why
   - Must list: File Management, Browser Automation, Document Creation, Custom Skills

7. **Setup Instructions** (numbered steps)
   - Step 1: Download Accomplish
   - Step 2: Connect AI provider
   - Step 3: Create custom skill (paste the prompt)
   - Step 4: Run the skill
   - Keep it under 2 minutes to set up

8. **Sample Output**
   - Show a real daily briefing document
   - Link to `sample-output/briefing-2026-02-16.md`

9. **Before & After**
   - Two-column comparison
   - Before: Screenshots/description of chaos
   - After: Screenshots/description of organization

10. **Tech Stack**
    - Accomplish (AI Desktop Agent)
    - AI Provider (user's choice)
    - No external dependencies

11. **Impact**
    - Time saved: 30+ min/day → 2 min
    - Files organized: automatic
    - Information: curated daily briefing

12. **Hackathon**
    - Built for "Automate Me If You Can" by WeMakeDevs
    - Link to hackathon page

**Style guidelines:**
- Use emojis for visual interest but don't overdo it
- Keep paragraphs SHORT (2-3 sentences max)
- Include the architecture diagram from this plan
- Be specific about numbers (time saved, files organized)
- NO filler content. Every sentence must add value.
- Under 300 lines total. Judges skim.

**Acceptance criteria:**
- [ ] README is under 300 lines
- [ ] All 12 sections present
- [ ] No filler or redundant content
- [ ] Clear setup instructions (under 5 steps)
- [ ] Architecture diagram included
- [ ] Compelling problem/solution narrative

---

### TASK 4: Write the Demo Script
**Assignee:** Any agent  
**Priority:** P1  
**Time:** 45 min  
**File:** `demo/demo-script.md`  

**What to do:**

Write a precise 3-minute demo video script. This is what Anurag will follow while recording.

**Scene structure:**

**Scene 1: The Problem (0:00–0:40)**
- Show messy ~/Downloads folder (20+ files, random names, mixed types)
- Show GitHub with unread notifications
- Show no daily plan or organization
- Narration: "Every morning starts the same way — a mess."
- Text overlay: "30+ minutes wasted before writing a single line of code"

**Scene 2: The Automation (0:40–2:00)**
- Open Accomplish app
- Type or select "Run Dev Day Autopilot"
- Show Accomplish processing:
  - Phase 1: Files being categorized and moved (show file explorer updating)
  - Phase 2: Browser opening, GitHub notifications loading, HN scraping
  - Phase 3: Daily briefing document being generated
- Show user approval prompts (Accomplish asks before each action)
- Speed up boring parts (2x-4x), keep key moments at 1x
- Narration: "One prompt. Accomplish handles everything."

**Scene 3: The Results (2:00–2:45)**
- Show organized ~/Downloads (clean subfolders)
- Show the generated daily briefing document (scroll through sections)
- Show GitHub activity summary in the briefing
- Show trending articles in the briefing
- Split screen: BEFORE (messy) vs AFTER (organized)
- Text overlay: "30 minutes → 2 minutes"

**Scene 4: Closing (2:45–3:00)**
- Show saving as custom skill in Accomplish
- Text: "Run it every morning. One click."
- Closing: "Dev Day Autopilot — built with Accomplish"
- Show Accomplish logo + hackathon branding

**Recording instructions:**
- Resolution: 1920x1080, 30fps minimum
- Use OBS Studio (free) or equivalent
- Record audio narration separately if possible (cleaner)
- Add background music (lo-fi beats, royalty-free)
- Keep total video ≤ 3 minutes strictly
- Export: MP4, H.264, ~8000 kbps

**Acceptance criteria:**
- [ ] Script covers exactly 3 minutes
- [ ] 4 clear scenes with timestamps
- [ ] Narration text written for each scene
- [ ] Recording setup instructions included
- [ ] Emphasizes all 4 Accomplish features visually

---

### TASK 5: Record & Edit Demo Video
**Assignee:** Anurag (manual task)  
**Priority:** P0 (most important deliverable)  
**Time:** 3-4 hours  

**What to do:**

1. **Prepare environment:**
   - Run `test-data/setup-test-downloads.sh` to create messy Downloads
   - Have Accomplish installed with AI provider connected
   - Have the "Dev Day Autopilot" skill created in Accomplish
   - Close all unnecessary apps
   - Clean desktop (only show what's needed)

2. **Record:**
   - Follow `demo/demo-script.md` scene by scene
   - Do 2-3 takes of each scene
   - Record narration (can be voiceover added later)

3. **Edit:**
   - Cut best takes together
   - Add text overlays at key moments
   - Add intro/outro slides
   - Speed up slow parts (file moving, browser loading)
   - Add subtle background music
   - Ensure total ≤ 3:00

4. **Export:**
   - MP4, 1920×1080, H.264
   - Upload to YouTube (unlisted) or keep as file for submission

**Acceptance criteria:**
- [ ] Video is ≤ 3 minutes
- [ ] Shows all 4 Accomplish features in action
- [ ] Clear before/after comparison
- [ ] Professional quality (good audio, smooth transitions)
- [ ] Time savings clearly visible

---

### TASK 6: Submit to Hackathon
**Assignee:** Anurag (manual task)  
**Priority:** P0  
**Time:** 30 min  

**What to do:**
1. Push all code to GitHub (public repo)
2. Go to https://wemakedevs.org/hack-all-february
3. Fill submission form:
   - Project name: "Dev Day Autopilot"
   - Description: "An Accomplish automation that organizes your Downloads, checks GitHub, scrapes dev news, and generates a daily briefing — all in under 2 minutes."
   - Demo video link
   - GitHub repo link
4. Share on social media:
   - Twitter/LinkedIn post tagging @wemakedevs @Accomplish_ai
   - Use #AutomateMeIfYouCan
   - Share demo video clip (30 sec teaser)

---

## Task Dependencies

```
TASK 1 (Setup) ──┐
                  ├──→ TASK 5 (Record Demo) ──→ TASK 6 (Submit)
TASK 2 (Skill)  ──┤
                  │
TASK 3 (README) ──┤
                  │
TASK 4 (Script) ──┘
```

Tasks 1-4 can be done in parallel. Task 5 requires all of 1-4. Task 6 requires 5.

---

## Timeline

| Day | Tasks | Hours |
|-----|-------|-------|
| Day 1 (Feb 16) | Tasks 1-4 in parallel | 4-5h |
| Day 2 (Feb 17) | Install Accomplish, test skill, iterate | 3-4h |
| Day 3 (Feb 18) | Record demo video (Task 5) | 3-4h |
| Day 4 (Feb 19) | Edit video, polish README | 2-3h |
| Day 5 (Feb 20) | Submit (Task 6) + social media | 1h |
| Buffer (Feb 21-22) | Fix any issues, re-record if needed | — |

---

## Key Rules for All Agents

1. **NO meta-documentation files.** No START_HERE.md, PROJECT_STRUCTURE.md, IMPLEMENTATION_COMPLETE.md. Just README + skill + test data + demo script. That's it.
2. **Keep it lean.** The project should have ≤8 files total. Quality over quantity.
3. **The skill prompt is everything.** If the skill prompt sucks, nothing else matters. Make it crystal clear.
4. **The demo video wins or loses.** 80% of judging is the 3-minute video. Every other file exists to support the demo.
5. **Test with Accomplish.** Don't write things that haven't been tested. If you can't test, mark it clearly.
6. **No placeholder content.** Every file should be complete and usable as-is.

---

## Final File Count Target

```
dev-day-autopilot/
├── README.md                          # 1. Project overview (judges read this)
├── IMPLEMENTATION_PLAN.md             # 2. This file (for internal coordination)
├── skill/
│   └── dev-day-autopilot.md           # 3. THE actual Accomplish skill prompt
├── test-data/
│   └── setup-test-downloads.sh        # 4. Creates messy Downloads for demo
├── sample-output/
│   └── briefing-2026-02-16.md         # 5. Example output document
└── demo/
    └── demo-script.md                 # 6. Video recording script
```

**6 files. That's it. Each one essential.**

---

## Success Metric

If a judge can:
1. Read the README in 2 minutes and understand the value
2. Watch the demo in 3 minutes and be impressed
3. Paste the skill into Accomplish and have it work

...then we win.