a-plus-onboard-correction
Installation
SKILL.md
Attendance Plus Onboard Correction
Generate one-off Ruby scripts to correct A+ entity configuration for a district. These scripts are throwaway artifacts -- copied to tmp/ on the target environment, dry-run to verify, then applied.
Step 1: Triage the Request
Parse the user's request into one or more entity corrections. A single request often contains multiple corrections.
| Business Language | Entity Type | Reference | Template |
|---|---|---|---|
| "code X needs is_suspension changed", "change absence type", "remap codes" | Absence code update | references/absence-codes.md |
assets/absence-code-update.md |
| "add code ISS", "create new absence code", table of new codes | Absence code create | references/absence-codes.md |
assets/absence-code-create.md |
| "remove code X", "retire/disable code", "discard obsolete codes" | Absence code discard | references/absence-codes.md |
assets/absence-code-discard.md |
| "school X has different start/end date", "earlier/later start/end" | Calendar: school year creation | references/calendar.md |
assets/calendar.md (Mode 1) |
| "add November 4th as non-attendance day", "add closure dates" | Calendar: NID addition | references/calendar.md |
assets/calendar.md (Mode 2 or 3) |
| "change tier thresholds", "add/remove tier", "adjust tier labels" | Tier update | references/tiers.md |
assets/tier-update.md |
Always read references/domain-api.md for API signatures, key types, and schema.
Related skills
More from dailydm/skills
shapeup
ShapeUp: Facilitate the complete ShapeUp workflow with triad collaboration
13hillchart
Hillchart: visualize project progress by analyzing the codebase
5frame
Frame: create a Pitch from a problem statement or idea
4plan
Plan: create an execution Plan from an approved Shaping doc
4shape
Shape: create a filled Shaping doc from an attached Pitch
4implement
Implement: execute a task from a Breakdown
4