| name | pre-flight-checklist |
| description | Check if task is already complete, verify dev server status and port, check TypeScript compilation status, verify required dependencies are installed, and load all required skills upfront. Use at the start of every task to ensure proper environment setup and avoid wasted effort. |
Pre-Flight Checklist
Overview
Systematic checklist to verify environment setup and task status before starting work. Prevents wasted effort on already-complete tasks and ensures proper environment configuration.
Checklist Items
1. Check if Task is Already Complete
Before starting work, verify task status:
- Read task file:
tasks/next_task.md
- Read progress file:
tasks/progress.txt
- Check completion status: Is task already marked complete?
- Verify success criteria: Are all criteria met?
If task is complete:
- Document verification
- Move to next task
- Don't redo completed work
Pattern:
cat tasks/next_task.md
cat tasks/progress.txt | grep -A 10 "US-XXX"
2. Verify Dev Server Status and Port
Before browser testing, verify server is running:
- Check if server is running: Look for process on port
- Detect actual port: Check
vite.config.ts, package.json, terminal output
- Verify server health: Poll server endpoint
- Start server if needed:
npm run dev
Reference: See dev-server-port-detection skill for port discovery patterns.
Pattern:
lsof -i :3000 || lsof -i :5173
grep -A 5 "server:" vite.config.ts
grep -i "port" package.json
curl -s http://localhost:3000 > /dev/null && echo "Server is running"
Backend / Server (for backend tasks)
Before the first API test:
- Check that the target port is free (e.g.
lsof -i :PORT) or that a single dev server is listening.
- Start command: use an explicit directory (e.g.
cd /absolute/path/to/backend && npm run dev).
- Optional: short-timeout health check (e.g.
curl -f http://localhost:PORT/api/health --max-time 5).
- Auth tasks: First register/login may be slow (e.g. bcrypt). Use request timeouts (e.g. 10–15 s) for register/login checks (e.g.
curl --max-time 10).
Path convention (monorepos)
- Backend library code lives under
backend/src/lib/, not backend/lib/.
- Confirm the backend app root for the repo before creating API or lib files.
3. Check TypeScript Compilation Status
Before making changes, verify current compilation status:
- Run TypeScript check:
npx tsc --noEmit
- Fix any existing errors: Don't add to broken codebase
- Verify compilation passes: Must pass before proceeding
Reference: See typescript-incremental-check skill for compilation patterns.
Pattern:
npx tsc --noEmit
4. Verify Required Dependencies are Installed
Before using packages, verify dependencies:
- Check
package.json: Required packages listed
- Check
node_modules: Packages installed
- Run
npm install if needed: Install missing dependencies
Pattern:
ls node_modules
npm install
npm list <package-name>
5. Load All Required Skills Upfront
Before starting implementation, discover and load skills:
- Search all skills:
search_skills("") to list all
- Load relevant skills: Load skills needed for task
- Reference skill documentation: Read skill docs before using
Reference: See agent-workflow-guidelines skill for skill discovery workflow.
Pattern:
search_skills("")
load_skill("phaser-game-testing")
load_skill("agent-browser")
load_skill("typescript-incremental-check")
Environment Validation Patterns
Pattern 1: Complete Pre-Flight Check
cat tasks/next_task.md
cat tasks/progress.txt
lsof -i :3000 || npm run dev &
npx tsc --noEmit
npm install
search_skills("")
load_skill("relevant-skill-1")
load_skill("relevant-skill-2")
Pattern 2: Quick Pre-Flight Check
For simple tasks, minimal check:
npx tsc --noEmit && echo "TypeScript OK"
lsof -i :3000 && echo "Server running" || npm run dev &
Pattern 3: Pre-Flight Script
Create reusable script:
#!/bin/bash
echo "Checking task status..."
cat tasks/next_task.md
echo "Checking TypeScript..."
npx tsc --noEmit
echo "Checking server..."
lsof -i :3000 || echo "Server not running, start with: npm run dev"
echo "Checking dependencies..."
npm list --depth=0
echo "Pre-flight check complete"
Common Issues and Solutions
Issue 1: Task Already Complete
Symptom: Progress shows task complete, all criteria met
Solution: Verify completion, document, move to next task
Issue 2: Server Not Running
Symptom: Browser connection fails, port not in use
Solution: Start server with npm run dev, wait for ready
Issue 3: TypeScript Errors
Symptom: Compilation fails with errors
Solution: Fix errors before proceeding, don't add to broken codebase
Issue 4: Missing Dependencies
Symptom: Import errors, module not found
Solution: Run npm install to install missing packages
Issue 5: Skills Not Loaded
Symptom: Missing patterns, inefficient workflows
Solution: Load relevant skills upfront, reference documentation
Workflow Integration
Start of Task Workflow
- Pre-flight check: Run complete checklist
- Fix any issues: Resolve environment problems
- Load skills: Discover and load relevant skills
- Begin implementation: Start task work
During Task Workflow
- After edits: Run TypeScript check immediately
- Before testing: Verify server is running
- Before completion: Verify all criteria met
Best Practices
- Always run pre-flight check: Don't skip verification
- Fix issues before starting: Don't work with broken environment
- Load skills upfront: Don't discover patterns mid-task
- Verify completion: Check if task already done
- Document findings: Note any issues or patterns discovered
Resources
agent-workflow-guidelines skill - General workflow guidelines
dev-server-port-detection skill - Port discovery patterns
typescript-incremental-check skill - Compilation patterns
task-verification-workflow skill - Task completion verification