skills/cali-product-workflow/skills-workflow/cali-plan-critique/SKILL.md
[Cali] Plan critique skill using audit checklists and frameworks. Reviews spec-product.md for gaps, risks, and improvements. Can be used standalone after Shape Up or as part of cali-product-workflow.
npx skillsauth add renatocaliari/agent-sync-public-skills cali-plan-critiqueInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill executes the Plan Critique phase. It can be used:
Read the references/ files to guide the process:
| File | Covers | When to read |
|---|---|---|
| references/PLAN-CRITIQUE-CONTEXT.md | Role definition, when to use, workflow position | Before starting — sets reviewer role |
| references/CHECKLISTS.md | Flow, state, affordance, data, system, feasibility checks | During analysis — primary checklist |
| references/critique-frameworks.md | Nielsen heuristics, emotional journey, cognitive load, personas, AI slop | During analysis — UX evaluation frameworks |
| references/audit-dimensions.md | 5 audit dimensions (a11y, perf, theming, responsive, anti-patterns) | During analysis — technical audit framework |
| references/auto-resolve-rules.md | Rules for automatic gap resolution | After analysis — for auto-resolve mode |
| references/output-format.md | Critique report format | After analysis — format output |
Launch a worker with checklists from references/:
references/ (CONTEXT.md role definition, CHECKLISTS.md primary checks, critique-frameworks.md UX, audit-dimensions.md technical).cali-product-workflow/{YYYY-MM-DD}/{_dir}/critiques/critique-report.mdCritique report is saved to:
.cali-product-workflow/{YYYY-MM-DD}/{_dir}/critiques/critique-report.md
Updated spec (after gap resolution):
.cali-product-workflow/{YYYY-MM-DD}/{_dir}/specs/spec-product_{v+1}.md
If any capability is unavailable, adapt using whatever tools your environment provides.
development
PocketBase v0.39+ development - API rules, auth, collections, SDK, realtime, files, Go/JS extending, deployment, production tuning.
tools
Auto-initialize structured documentation for any project using lat.md (knowledge graph of markdown files with [[wiki links]], // @lat: code refs, and semantic search). Detects cali-product-workflow artifacts (spec-product.md, spec-tech.md, critiques) and uses them as seed material. Falls back to extracting business rules, architecture, and design decisions directly from the codebase. Use when a project lacks structured documentation or when lat.md/ is missing. After seeding, lat.md extension hooks keep documentation alive automatically.
testing
[Cali] Server security audit and hardening for private servers behind Tailscale. Use when: auditing server security, hardening SSH/firewall/Docker, checking for vulnerabilities, setting up fail2ban, reviewing port exposure, or responding to security alerts. Covers 6 layers: CloudFlare, UFW, Tailscale, SSH, Docker, Application. Triggers: "server security", "security audit", "harden server", "SSH hardening", "firewall rules", "UFW config", "fail2ban", "port security", "Docker security", "vulnerability check", "security review".
tools
Run supply chain security scans before installing packages or before releases. Triggers when: user installs a package (npm, pip, go get, brew), user asks to 'scan dependencies', 'check vulnerabilities', 'supply chain', 'security audit', 'run trivy', 'run socket', or before any release/deployment. Also triggers on mentions of: socket.dev, trivy, OSV-scanner, dotenvx, CVE, dependency audit. Covers all four tools with concrete commands.