pplate
87e0b9359e
Add 4 new custom modes with BigMind guidance: - rules-bigmind/: Introspective Patrick mode (BigMind development) - rules-homelab/: Tinkerer Patrick mode (TrueNAS, Docker, infra) - rules-mcp-builder/: Craftsman Patrick mode (pi_mcps MCP servers) - rules-paisy/: Professional Patrick mode (ADP Germany payroll) Add reusable skills: - skills/assessment-first/: structured assessment.md before implementation - skills/bigmind-session-ritual/: mandatory session start/end ritual - skills/gitea-push/: conventional commit + Gitea push workflow - skills/new-mcp-server/: FastMCP scaffold procedure - skills-bigmind/, skills-homelab/, skills-mcp-builder/, skills-paisy/: mode-specific skill dirs Update existing rules: - rules-architect, rules-ask, rules-code, rules-debug, rules-orchestrator: add BigMind session guidance (search before task, announce focus, hypotheses) Add plans/MODES_AND_SKILLS_PLAN.md: full architecture document
85 lines
2.4 KiB
Markdown
85 lines
2.4 KiB
Markdown
---
|
|
name: paisy-assessment
|
|
description: Creates a structured assessment markdown document for an ADP Germany Paisy Jira ticket before any code is written. Use this skill at the start of every ESIDEPAISY ticket — covers root cause, affected files, risks, and implementation plan in German-compatible format.
|
|
---
|
|
|
|
# Paisy Assessment
|
|
|
|
## When to use
|
|
Every non-trivial ESIDEPAISY Jira ticket before touching any code. This is mandatory for Paisy work.
|
|
|
|
## When NOT to use
|
|
- Trivial config/text fixes without code changes
|
|
- A prior assessment already exists for this ticket
|
|
|
|
## Inputs required
|
|
- **Ticket ID** — e.g., `ESIDEPAISY-12021`
|
|
- **Ticket title** — from Jira
|
|
- **Module** — e.g., `eau`, `eubp`, `fex`, `common/beitragssatzdatei`
|
|
- **Error logs or symptoms** — stack traces, log output, reproduction steps
|
|
|
|
## Workflow
|
|
|
|
### Step 1 — Search BigMind for known patterns
|
|
```
|
|
memory_search_facts("ESIDEPAISY {module}")
|
|
memory_search_facts("bug-pattern {symptom keyword}")
|
|
memory_search_chunks("{error keyword}")
|
|
```
|
|
|
|
### Step 2 — Name and locate the file
|
|
Convention: `{MODULE}_{TICKET}_Assessment.md`
|
|
Location: `java/modules/.../docs/` within the affected module, or `java/modules/cs-modules/{module}/docs/`
|
|
|
|
### Step 3 — Write the assessment document
|
|
|
|
```markdown
|
|
# Assessment: {Ticket Title}
|
|
*Autor: Lumen | Datum: YYYY-MM-DD | Ticket: ESIDEPAISY-XXXXX*
|
|
|
|
## Zusammenfassung
|
|
[1-2 sentences in German summarizing the problem]
|
|
|
|
## Root Cause Analysis
|
|
[Technical analysis — can be in English for code-level detail]
|
|
|
|
### Bekannte Muster
|
|
[Reference any similar bugs from BigMind memory]
|
|
|
|
## Betroffene Dateien
|
|
| Datei | Zeile | Änderung |
|
|
|-------|-------|----------|
|
|
| ClassName.java | 428 | Add null-check |
|
|
|
|
## Risiken
|
|
- [Risk 1]
|
|
- [Risk 2]
|
|
|
|
## Alternativen
|
|
### Option A (gewählt): ...
|
|
### Option B: ...
|
|
|
|
## Implementierungsplan
|
|
1. [Step 1]
|
|
2. [Step 2]
|
|
|
|
## Offene Fragen
|
|
- [ ] Q1: [Question] → @{person}
|
|
```
|
|
|
|
### Step 4 — Store assessment location in BigMind
|
|
```
|
|
memory_store_fact("codebase", "ESIDEPAISY-XXXXX assessment at {path}")
|
|
```
|
|
|
|
### Step 5 — Create feature branch
|
|
```bash
|
|
git checkout -b feature/ESIDEPAISY-XXXXX-short-description
|
|
# or for bugs:
|
|
git checkout -b bugfix/eau/ESIDEPAISY-XXXXX-short-description
|
|
```
|
|
|
|
## Troubleshooting
|
|
- If root cause is unclear: write "TBD — pending log analysis" and open a question in the doc
|
|
- If blocked on another ticket: note the blocker in Offene Fragen and set ticket status to "Blocked"
|