返回 Skill 列表
extension
分类: 开发与工程无需 API Key

plan-lint

在编码前根据文档约束验证计划。请在文档发现后、实施前使用。返回PASS、WARN或FAIL,并附带具体问题。这是两阶段流程中的第一阶段。

person作者: jakexiaohubgithub

Plan Lint

Ensure plan is doc-consistent before coding. Gate 1 of 2-gate flow.

When to Use

  • After /doc-discovery, before coding
  • When reviewing someone else's plan
  • Before spawning implementation agents
  • When user asks "is this plan safe?"

Required Plan Elements

| Element | Required | |---------|----------| | Primary Feature | Yes | | Impacted Features | Yes | | User-Facing Changes | Yes | | Files/Surfaces to modify | Yes | | Data Impact (tables, RLS) | If applicable | | Invariants (min 3) | Yes | | Test Plan | Yes | | Docs to Update | Yes |

Checks

  1. Feature Coverage: Primary named? Exists in index? Coupled features included?
  2. Invariant Coverage: At least 3? Match feature docs? High-risk addressed?
  3. Data Safety: Tables listed? RLS documented? Migration + rollback plan?
  4. Test Coverage: Verification steps? Workflow smoke test? Regression areas?
  5. Workflow Impact: Affected workflows identified? No journeys broken?
  6. Page Standards (for new pages):
    • [ ] Plan includes AIPanel with agentType
    • [ ] Plan includes contextScope configuration
    • [ ] No solid backgrounds on page containers
    • [ ] Canvas Header follows h-24, bg-white/5 pattern
  7. Org-Scoped Features (if org-specific):
    • [ ] org_id column included in relevant tables
    • [ ] RLS policies enforce org isolation
    • [ ] RAG scope includes orgId filtering

Blast Radius

| Factor | Points | |--------|--------| | Auth/RLS | +3 | | Billing/credits | +3 | | AI/prompts | +2 | | Schema/migrations | +2 | | 3+ features | +2 | | Org-scoped content | +2 | | New page without AI Panel spec | +2 | | Shared components | +1 | | User workflow change | +1 |

0-2: Low → Standard review 3-5: Medium → Careful review 6+: High → Doc Agent validation required

Output

## Plan Lint: [PASS/WARN/FAIL]

**Blast Radius**: [score] ([low/medium/high])

### Validation
- [x/] Primary feature: [name]
- [x/] Impacted features: [count]
- [x/] Invariants: [count]
- [x/] Test plan: [status]
- [x/] Workflow impact: [status]

### Issues (if any)
1. **[Category]**: [Problem] → [Fix]

### Ready to Implement
[Yes / Conditional / No]

Related