Why it matters
A concrete file-based business workflow emerged from the independent audit. Its reported time savings remain personal experience, while the public prompts support further inspection.
For Solo consultants, Knowledge workers.
Sources & further reading
GitHub · implementation
Personal OS starter and upgrade prompts ↗
README and v0.7 changelog read: protected raw notes, generated briefs and review queues. No agent was run.
Nick Zervoudis · page checked 2026-10-16
Web · analysis
The consultant who runs his business from text files ↗
September 30 case study read and followed to its author’s repository. Outcomes are self-reported.
Create With · page checked 2026-10-16
More sources reviewed (1)
Web · analysis
Create With newsletter archive ↗
Four archive entries sampled after the main sweep; two within the rolling window were opened.
Create With · page checked 2026-10-16
Coverage note: Public repository and creator case study read. The linked webinar was identified but not reviewed, and no independent execution was established.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
Nick Zervoudis’ Personal OS keeps raw daily notes in one place and asks a coding agent to maintain a separate brief, task records and review queue. The public v0.7 starter and upgrade prompts work with a Markdown vault. This can interest solo consultants who want inspectable files and draft handoffs. The README and September case study were read October 16. Terminal comfort and model access are required; mobile use and integrations have known rough edges. No workflow was executed.