SKILL PLAN · DETERMINISTIC
A small plan for a real job
Start with the minimum useful stack. Add nothing unless it has a clear responsibility in the run.
- Task
- Web app testing
- Agent
- Codex
- Priority
- Balanced
Change any option, then update this plan. Rules + reviewed metadata only. No LLM. Same inputs produce the same plan.
01Core execution
Native · Codex
playwright-workflows
Exercises the real user flow in a browser. Open playwright-workflows profile and install guide ↗Review permissions, limitations, and evidence
- Agent fit
- Native · Codex
- Main limitation
- Detailed package files are not fully catalogued.
- First risk
- Review before install · Medium
- Source
- Editorial source
02Guardrail
Native · Codex
web-design-guidelines
Defines scope and prevents a broad, unfocused test run. Open web-design-guidelines profile and install guide ↗Review permissions, limitations, and evidence
- Agent fit
- Native · Codex
- Main limitation
- It depends on network access and a live guideline document whose contents can change over time.
- First risk
- Rule drift or context-free findings · Medium
- Source
- Pinned source · 063bee94
03Evidence
Native · Codex
Minimal Run and Audit
Retains visual and runtime evidence for review. Open Minimal Run and Audit profile and install guide ↗Review permissions, limitations, and evidence
- Agent fit
- Native · Codex
- Main limitation
- Detailed package files are not fully catalogued.
- First risk
- Review before install · Medium
- Source
- Pinned source · fb3ccdf5
Core executionwebapp-testing
- Choose this when
- you want stronger published documentation to start from
- Tradeoff to check
- It assumes Python Playwright and a runnable local application are available.
Inspect webapp-testing ↗Guardrailcontext-map
- Choose this when
- this role's workflow fits your project better after you inspect the tradeoff
- Tradeoff to check
- The workflow is intentionally brief and may miss dynamic dependencies or runtime ownership.
Inspect context-map ↗Evidencepr-screenshots
- Choose this when
- you want stronger published documentation to start from
- Tradeoff to check
- GitHub has no clean public API for PR-description image upload in this workflow.
Inspect pr-screenshots ↗ Combined permission budget
This is the union of declared permissions across the plan. Review each package before installation.
Browser controlRun commandsWrite screenshotsRead frontend filesRead research codeRun bounded commandsWrite audit artifacts
Finish with evidence
Prove the critical user flow works in a real browser and leave repeatable evidence.
Use test data and a local or explicitly approved environment.
- 3-step acceptance check
- Run one critical flow from a clean browser state.
- Assert the expected page state, not only a successful click.
- Save the failure signal needed to reproduce any defect.
- Stop conditions
- The test requires production credentials or personal data.
- The script performs destructive actions without isolation.
- A flaky result is reported as a pass.