popoffvg/work-start
.pi/agent/skills/work-start/SKILL.md
Start new work. The /work:start command handler in the work extension does all initialization automatically — no skill injection needed. This file exists for documentation only.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles work-startInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 2:26 AM6.9s1 file scanned
SKILL.md
- name:
- work-start
- description:
- >
- Start new work. The /work:
- start command handler in the work extension
work:start
Handled entirely by the work extension:
- Detects branch and parses work-id
- Creates
_notes/withgit init - Creates
worklog.md - Commits initial state
- Creates
.pi/work.settings.jsonwith phase=plan - Injects
work:planskill to start planning
No user questions asked — planning happens in the plan phase.
Autoresearch rules
Eval checklist:
- Was
_notes/directory created withgit init? - Was
.pi/work.settings.jsoncreated with phase=plan? - Did the extension inject the work:plan skill after initialization?
- Were zero user questions asked during start (planning happens in plan phase)?
Test inputs:
- "Start new work on existing feature branch"
- "Start new work from main branch"
- "Start work when _notes/ already exists from previous run"
Can change: initialization steps, default settings values, worklog template Cannot change: automatic flow (no user questions), _notes/ as working directory, plan phase as initial phase Min sessions before eval: 5 Runs per experiment: 3
Related Skills
popoffvg/improve-claude-local
tools
VerifiedTrustedCommunity
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
2SKILL.mdUpdated Jun 25, 2026
popoffvg/workflow
testing
VerifiedTrustedCommunity
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/code
development
VerifiedTrustedCommunity
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/red-green-refactor
development
VerifiedTrustedCommunity
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
2SKILL.mdUpdated Jun 18, 2026