Skill: Light Mode
Tier: 2 (Load on specific trigger) Purpose: Provide streamlined instructions for trivial, low-risk tasks.
Definition of "Low Risk"
A task qualifies for Light Mode if ALL of the following are true:
- No new files created (except minor config tweaks).
- No database schema changes.
- No API contract changes (endpoints, request/response formats).
- No new dependencies added.
- No modifications to files matching:
auth*,payment*,crypto*,security*. - Estimated implementation time: < 30 minutes.
If ANY condition is false, ESCALATE to standard pipeline.
Instructions by Role
For Analyst
- Mark the TASK title with
[LIGHT]tag. - Keep requirements minimal — focus on "What is broken?" and "What is the expected fix?".
- Skip detailed acceptance criteria if the fix is obvious.
For Developer
- Do not overengineer. Fix the issue directly.
- Do not refactor unrelated code.
- Run tests after every change.
- If you discover complexity (DB migration, API change), STOP and request workflow switch.
For Code Reviewer
- Focus on correctness and tests.
- Skip architectural nitpicks unless they are critical bugs.
- Perform a basic security sanity check:
- No credentials or secrets in code.
- No new dependencies without approval.
- No changes to auth/payment/crypto files.
- If security concerns arise, ESCALATE to
skill-security-audit.
Escalation Protocol
If at any point the task complexity exceeds Light Mode scope:
- Inform the user: "This task requires standard pipeline due to [REASON]."
- Switch workflow: Call
/01-start-featureinstead. - The
[LIGHT]tag should be removed from the TASK.
Safety Rules
The following files are PROHIBITED from Light Mode modifications:
**/auth/**,**/authentication/****/payment/**,**/billing/****/crypto/**,**/encryption/****/security/**.env,*.pem,*.key
If the task touches these files, ALWAYS escalate to standard pipeline with Security Audit.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.