[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754GEAPC6CCCDKNYCB9SHY5":3,"skill-same:01M754GEAPC6CCCDKNYCB9SHY5":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M754GEAPC6CCCDKNYCB9SHY5","planning-standards-kp",null,"Fonte da verdade do modelo RA9 (Rule-Aligned 9-Section) para templates de planejamento Epic\u002FStory\u002FTask. Define as 9 seções fixas, granularidade por nível, micro-template Decision Rationale, e mapeamento rule ↔ seção.","review-bench\u002Federcnj_ia-dev-environment","review-bench","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286778065?v=4","01M7517F9NTEPDZDAXJBR30FWT","ReviewBench","01M7517FAC9F4P7TGWCNJ8VYVW",0,"MIT","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fplanning-standards-kp\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: planning-standards-kp\ndescription: \"Fonte da verdade do modelo RA9 (Rule-Aligned 9-Section) para templates de planejamento Epic\u002FStory\u002FTask. Define as 9 seções fixas, granularidade por nível, micro-template Decision Rationale, e mapeamento rule ↔ seção.\"\nuser-invocable: false\nrequires-capabilities: []\ncontext-budget: medium\n---\n\n> 🔒 **INTERNAL KNOWLEDGE PACK** — Referenced by plan skills (`x-epic-create`, `x-epic-decompose`, `x-plan-story`, `x-plan-task`). Not user-invocable.\n\n# Knowledge Pack: Planning Standards (RA9 — Rule-Aligned 9-Section)\n\n## Purpose\n\nSingle source of truth for the RA9 model. Every plan artifact (Epic, Story, Task) MUST contain the 9 fixed sections in the canonical order below. Skills reference this KP via `@planning-standards-kp` instead of duplicating the contract inline.\n\n---\n\n## 1. Contexto & Escopo\n\n**Rule anchor:** Rule 01 (Project Identity)\n**KP anchor:** N\u002FA (project-identity)\n**Required at:**\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | 3-5 sentence description: what is built, problem solved, scope boundaries (in\u002Fout). Jira key. |\n| Story | User story sentence (`As \u003Cpersona>, I want \u003Caction> so that \u003Cbenefit>`). 2-3 paragraphs of context. Entrega de Valor subsection. |\n| Task | Single objective sentence. What this task implements specifically. |\n\n**Granularity note:** Epic = vision + boundaries; Story = feature + value; Task = single implementation unit.\n\n---\n\n## 2. Packages (Hexagonal)\n\n**Rule anchor:** Rule 04 (Architecture Summary)\n**KP anchor:** `knowledge\u002Farchitecture.md`\n**Required at:** Epic, Story, Task (minimum 1 layer declared)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Full package catalog across all 5 layers for all stories in the epic. Mark untouched layers with `—`. Declare dependency direction explicitly: `adapter → application → domain`. |\n| Story | Packages touched by this story. New classes\u002Finterfaces per layer. Dependency direction statement. |\n| Task | 1-3 specific files. Layer classification. |\n\n**5 canonical layers:**\n1. `domain\u002F` — entities, value objects, engines, ports\n2. `application\u002F` — use cases, orchestration\n3. `adapter\u002Finbound\u002F` — REST, gRPC, CLI handlers, DTOs, mappers\n4. `adapter\u002Foutbound\u002F` — database, external clients, entities, mappers\n5. `infrastructure\u002F` — framework config, observability wiring\n\n**Example (Story level):**\n```\n### Domain Layer\n- `domain\u002Fpayment\u002Fmodel\u002FPaymentOrder.java` — new entity\n- Dependency direction: application → domain (inward only)\n\n### Application Layer\n- `application\u002Fpayment\u002FProcessPaymentUseCase.java` — new use case\n- Port: `domain\u002Fpayment\u002Fport\u002FPaymentRepository.java`\n\n### Adapter Inbound\n- `adapter\u002Finbound\u002Frest\u002FPaymentController.java` — new REST handler\n- DTO: `adapter\u002Finbound\u002Frest\u002Fdto\u002FPaymentRequest.java`\n\n### Adapter Outbound\n- `adapter\u002Foutbound\u002Fdatabase\u002FJpaPaymentRepository.java` — implements port\n\n### Infrastructure\n— (no changes)\n```\n\n---\n\n## 3. Contratos & Endpoints\n\n**Rule anchor:** Rule 03 (Coding Standards)\n**KP anchor:** `knowledge\u002Fprotocols.md`\n**Required at:** Epic (summary), Story (full contract), Task (single handler\u002Fmethod signature)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | List of all endpoints\u002Fevents exposed by the epic (method + path + protocol). |\n| Story | Full request\u002Fresponse schema (field, type, M\u002FO, validation, example). Error codes (RFC 7807). Event schema when event-driven. |\n| Task | Single method signature or handler I\u002FO contract. |\n\n**Formats:** REST → OpenAPI fields; Event → AsyncAPI payload; gRPC → Protobuf message definition.\n\n---\n\n## 4. Materialização SOLID\n\n**Rule anchor:** Rule 03 (Coding Standards)\n**KP anchor:** `knowledge\u002Fcoding-standards.md`\n**Required at:** Epic (transversal business rules), Story (local rules), Task (SOLID constraints)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Cross-cutting business rules table (`RULE-NNN | Title | Description`). Applied to multiple stories. |\n| Story | Business rules applicable to this story (reference epic RULE-NNN by ID). Local constraints. |\n| Task | SOLID principles applicable (SRP: one reason to change; OCP: new behavior = new class; etc.). Coding standard constraints (≤25 lines\u002Fmethod, ≤250 lines\u002Fclass). |\n\n---\n\n## 5. Quality Gates\n\n**Rule anchor:** Rule 05 (Quality Gates)\n**KP anchor:** `knowledge\u002Ftesting.md`\n**Required at:** Epic (global DoR\u002FDoD), Story (local DoR\u002FDoD + Gherkin), Task (DoD checklist)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Global DoR (pre-conditions for any story). Global DoD (coverage ≥95% line, ≥90% branch; TDD compliance; smoke tests; CHANGELOG). |\n| Story | Local DoR + local DoD. Gherkin scenarios (subsection 5.2 Acceptance Criteria). TPP order: degenerate → unconditional → conditions → iterations → edge cases. |\n| Task | DoD checklist (code implemented, test Red→Green→Refactor, `{{COMPILE_COMMAND}}` green, contracts respected, atomic commit). |\n\n**Coverage threshold (non-negotiable):** ≥ 95% line, ≥ 90% branch (Rule 05 absolute gate).\n\n---\n\n## 6. Segurança\n\n**Rule anchor:** Rule 06 (Security Baseline)\n**KP anchor:** `knowledge\u002Fsecurity\u002Findex.md`\n**Required at:** Epic (global security rules), Story (relevant security checks), Task (code-level checks)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Security policies that apply to all stories. Sensitive data classification. |\n| Story | OWASP checks applicable. Input validation strategy. Authentication\u002Fauthorization requirements. |\n| Task | Code-level security: no SQL concatenation, no hardcoded credentials, no `Math.random()` for tokens, path normalization for file ops. |\n\n**Minimum required per Story:** identify whether task touches user input, file I\u002FO, auth tokens, or external calls; if yes, declare the security control.\n\n---\n\n## 7. Observabilidade\n\n**Rule anchor:** Rule 07 (Operations Baseline)\n**KP anchor:** `knowledge\u002Fobservability\u002Findex.md`\n**Required at:** Epic (global SLOs), Story (logging\u002Ftracing requirements), Task (structured logging)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | SLO\u002FSLI definitions. Health check requirements. Shutdown timeout. |\n| Story | Structured logging fields. Correlation ID propagation. Metrics to emit. |\n| Task | Specific log statements with level and message. Trace propagation. |\n\n**Required fields in structured logs:** `timestamp`, `level`, `message`, `trace_id`, `span_id`, `service`.\n\n---\n\n## 8. Decision Rationale\n\n**Rule anchor:** Rule 24 (Execution Integrity)\n**KP anchor:** N\u002FA\n**Required at:** Epic (mandatory, ≥1 item), Story (mandatory, ≥1 item), Task (optional — `N\u002FA — \u003Cshort reason>` accepted)\n\n### Micro-template (4-line format — MANDATORY for each decision)\n\n```markdown\n**Decisão:** \u003Cstatement of the decision made>\n**Motivo:** \u003Cwhy this option was chosen — technical or business constraint>\n**Alternativa descartada:** \u003Cwhat was rejected and why>\n**Consequência:** \u003Ctrade-off or future implication>\n```\n\n### Validation rules\n\n| Level | Rule |\n| :--- | :--- |\n| Epic | Section 8 MUST have ≥1 filled item using the 4-line micro-template. Placeholders (`{{...}}`), `TODO`, empty body → `RA9_RATIONALE_EMPTY` audit failure. |\n| Story | Same as Epic. |\n| Task | `N\u002FA — \u003Creason>` is accepted. If a design decision was made (retry count, lazy vs eager, algorithm choice), use the micro-template. |\n\n### Example (Story level)\n\n```markdown\n**Decisão:** Use `JpaPaymentRepository` as the outbound adapter instead of a custom JDBC template.\n**Motivo:** Spring Data JPA provides built-in transaction management and reduces boilerplate by 60% for this simple CRUD pattern.\n**Alternativa descartada:** Custom JDBC — rejected because it requires manual transaction handling and duplicates RowMapper code already present in 3 other adapters.\n**Consequência:** Binds the adapter to Spring Data JPA; future migration to reactive persistence requires adapter rewrite, not domain change.\n```\n\n---\n\n## 9. Dependências & File Footprint\n\n**Rule anchor:** Rule 14 (Project Scope)\n**KP anchor:** `knowledge\u002Fparallelism-heuristics.md`\n**Required at:** Epic (story index + dependency DAG), Story (task list + file footprint), Task (file list + `depends-on`)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Story index table with dependency column. Implementation map reference. |\n| Story | Task list (Section 8). `## File Footprint` block for parallelism evaluation (Rule 04 EPIC-0041). |\n| Task | Explicit file list (`write:` \u002F `read:` \u002F `regen:`). `Dependencies` field (other task IDs or `—`). |\n\n### File Footprint format (Story level — RULE-004 EPIC-0041)\n\n```markdown\n## File Footprint\n\nwrite:\n  - src\u002Fmain\u002Fjava\u002Fdev\u002Fiadev\u002Fdomain\u002Fpayment\u002Fmodel\u002FPaymentOrder.java\n  - src\u002Fmain\u002Fjava\u002Fdev\u002Fiadev\u002Fadapter\u002Finbound\u002Frest\u002FPaymentController.java\nread:\n  - src\u002Fmain\u002Fjava\u002Fdev\u002Fiadev\u002Fdomain\u002Fpayment\u002Fport\u002FPaymentRepository.java\nregen:\n  - src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002F.claude\u002Fskills\u002Fx-epic-create\u002FSKILL.md\n```\n\n---\n\n## Granularity Summary Table\n\n| Section | Epic depth | Story depth | Task depth |\n| :--- | :--- | :--- | :--- |\n| 1. Contexto & Escopo | Vision + boundaries (3-5 sentences) | User story + context (2-3 paragraphs) | Single objective (1 sentence) |\n| 2. Packages (Hexagonal) | Full catalog all 5 layers | Story-scoped packages | 1-3 specific files |\n| 3. Contratos & Endpoints | Endpoint summary list | Full request\u002Fresponse schema | Single handler signature |\n| 4. Materialização SOLID | Cross-cutting business rules table | Story rules (RULE-NNN refs) | SOLID constraints per method |\n| 5. Quality Gates | Global DoR\u002FDoD | Local DoR\u002FDoD + Gherkin | DoD checklist |\n| 6. Segurança | Global security policies | OWASP checks + auth requirements | Code-level security rules |\n| 7. Observabilidade | SLO\u002FSLI definitions | Logging + tracing requirements | Specific log statements |\n| 8. Decision Rationale | ≥1 item (mandatory) | ≥1 item (mandatory) | N\u002FA accepted |\n| 9. Dependências & File Footprint | Story index + DAG | Task list + File Footprint block | File list + depends-on |\n\n---\n\n## Rule ↔ Section Mapping\n\n| Rule | Section(s) | Enforcement |\n| :--- | :--- | :--- |\n| Rule 01 — Project Identity | 1. Contexto & Escopo | Story persona must match domain |\n| Rule 03 — Coding Standards | 3. Contratos, 4. SOLID | Hard limits (≤25 lines, ≤250 class) |\n| Rule 04 — Architecture | 2. Packages | Dependency direction mandatory |\n| Rule 05 — Quality Gates | 5. Quality Gates | Absolute coverage gate (95\u002F90) |\n| Rule 06 — Security | 6. Segurança | At least one control per user-input story |\n| Rule 07 — Operations | 7. Observabilidade | Structured logging fields required |\n| Rule 14 — Project Scope | 9. Dependências | File footprint block in stories |\n| Rule 24 — Execution Integrity | 8. Decision Rationale | 4-line micro-template mandatory |\n\n---\n\n## Audit Rules (RA9 CI enforcement — RULE-006 EPIC-0056)\n\n| Code | Applies to | Fails when |\n| :--- | :--- | :--- |\n| `RA9_SECTIONS_MISSING` | Epic, Story, Task | Any of the 9 `## N. \u003Cname>` headers absent |\n| `RA9_RATIONALE_EMPTY` | Epic, Story (NOT Task) | Section 8 present but body is empty, `{{...}}`, or `TODO` |\n| `RA9_PACKAGES_MISSING` | Epic, Story, Task | Section 2 present but all 5 layers marked `—` |\n\nEscape hatch: `\u003C!-- audit-exempt -->` on the line immediately before the artifact (rare, reviewed exceptions only).\n","> 🔒 **INTERNAL KNOWLEDGE PACK** — Referenced by plan skills (`x-epic-create`, `x-epic-decompose`, `x-plan-story`, `x-plan-task`). Not user-invocable.\n\n# Knowledge Pack: Planning Standards (RA9 — Rule-Aligned 9-Section)\n\n## Purpose\n\nSingle source of truth for the RA9 model. Every plan artifact (Epic, Story, Task) MUST contain the 9 fixed sections in the canonical order below. Skills reference this KP via `@planning-standards-kp` instead of duplicating the contract inline.\n\n---\n\n## 1. Contexto & Escopo\n\n**Rule anchor:** Rule 01 (Project Identity)\n**KP anchor:** N\u002FA (project-identity)\n**Required at:**\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | 3-5 sentence description: what is built, problem solved, scope boundaries (in\u002Fout). Jira key. |\n| Story | User story sentence (`As \u003Cpersona>, I want \u003Caction> so that \u003Cbenefit>`). 2-3 paragraphs of context. Entrega de Valor subsection. |\n| Task | Single objective sentence. What this task implements specifically. |\n\n**Granularity note:** Epic = vision + boundaries; Story = feature + value; Task = single implementation unit.\n\n---\n\n## 2. Packages (Hexagonal)\n\n**Rule anchor:** Rule 04 (Architecture Summary)\n**KP anchor:** `knowledge\u002Farchitecture.md`\n**Required at:** Epic, Story, Task (minimum 1 layer declared)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Full package catalog across all 5 layers for all stories in the epic. Mark untouched layers with `—`. Declare dependency direction explicitly: `adapter → application → domain`. |\n| Story | Packages touched by this story. New classes\u002Finterfaces per layer. Dependency direction statement. |\n| Task | 1-3 specific files. Layer classification. |\n\n**5 canonical layers:**\n1. `domain\u002F` — entities, value objects, engines, ports\n2. `application\u002F` — use cases, orchestration\n3. `adapter\u002Finbound\u002F` — REST, gRPC, CLI handlers, DTOs, mappers\n4. `adapter\u002Foutbound\u002F` — database, external clients, entities, mappers\n5. `infrastructure\u002F` — framework config, observability wiring\n\n**Example (Story level):**\n```\n### Domain Layer\n- `domain\u002Fpayment\u002Fmodel\u002FPaymentOrder.java` — new entity\n- Dependency direction: application → domain (inward only)\n\n### Application Layer\n- `application\u002Fpayment\u002FProcessPaymentUseCase.java` — new use case\n- Port: `domain\u002Fpayment\u002Fport\u002FPaymentRepository.java`\n\n### Adapter Inbound\n- `adapter\u002Finbound\u002Frest\u002FPaymentController.java` — new REST handler\n- DTO: `adapter\u002Finbound\u002Frest\u002Fdto\u002FPaymentRequest.java`\n\n### Adapter Outbound\n- `adapter\u002Foutbound\u002Fdatabase\u002FJpaPaymentRepository.java` — implements port\n\n### Infrastructure\n— (no changes)\n```\n\n---\n\n## 3. Contratos & Endpoints\n\n**Rule anchor:** Rule 03 (Coding Standards)\n**KP anchor:** `knowledge\u002Fprotocols.md`\n**Required at:** Epic (summary), Story (full contract), Task (single handler\u002Fmethod signature)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | List of all endpoints\u002Fevents exposed by the epic (method + path + protocol). |\n| Story | Full request\u002Fresponse schema (field, type, M\u002FO, validation, example). Error codes (RFC 7807). Event schema when event-driven. |\n| Task | Single method signature or handler I\u002FO contract. |\n\n**Formats:** REST → OpenAPI fields; Event → AsyncAPI payload; gRPC → Protobuf message definition.\n\n---\n\n## 4. Materialização SOLID\n\n**Rule anchor:** Rule 03 (Coding Standards)\n**KP anchor:** `knowledge\u002Fcoding-standards.md`\n**Required at:** Epic (transversal business rules), Story (local rules), Task (SOLID constraints)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Cross-cutting business rules table (`RULE-NNN | Title | Description`). Applied to multiple stories. |\n| Story | Business rules applicable to this story (reference epic RULE-NNN by ID). Local constraints. |\n| Task | SOLID principles applicable (SRP: one reason to change; OCP: new behavior = new class; etc.). Coding standard constraints (≤25 lines\u002Fmethod, ≤250 lines\u002Fclass). |\n\n---\n\n## 5. Quality Gates\n\n**Rule anchor:** Rule 05 (Quality Gates)\n**KP anchor:** `knowledge\u002Ftesting.md`\n**Required at:** Epic (global DoR\u002FDoD), Story (local DoR\u002FDoD + Gherkin), Task (DoD checklist)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Global DoR (pre-conditions for any story). Global DoD (coverage ≥95% line, ≥90% branch; TDD compliance; smoke tests; CHANGELOG). |\n| Story | Local DoR + local DoD. Gherkin scenarios (subsection 5.2 Acceptance Criteria). TPP order: degenerate → unconditional → conditions → iterations → edge cases. |\n| Task | DoD checklist (code implemented, test Red→Green→Refactor, `{{COMPILE_COMMAND}}` green, contracts respected, atomic commit). |\n\n**Coverage threshold (non-negotiable):** ≥ 95% line, ≥ 90% branch (Rule 05 absolute gate).\n\n---\n\n## 6. Segurança\n\n**Rule anchor:** Rule 06 (Security Baseline)\n**KP anchor:** `knowledge\u002Fsecurity\u002Findex.md`\n**Required at:** Epic (global security rules), Story (relevant security checks), Task (code-level checks)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Security policies that apply to all stories. Sensitive data classification. |\n| Story | OWASP checks applicable. Input validation strategy. Authentication\u002Fauthorization requirements. |\n| Task | Code-level security: no SQL concatenation, no hardcoded credentials, no `Math.random()` for tokens, path normalization for file ops. |\n\n**Minimum required per Story:** identify whether task touches user input, file I\u002FO, auth tokens, or external calls; if yes, declare the security control.\n\n---\n\n## 7. Observabilidade\n\n**Rule anchor:** Rule 07 (Operations Baseline)\n**KP anchor:** `knowledge\u002Fobservability\u002Findex.md`\n**Required at:** Epic (global SLOs), Story (logging\u002Ftracing requirements), Task (structured logging)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | SLO\u002FSLI definitions. Health check requirements. Shutdown timeout. |\n| Story | Structured logging fields. Correlation ID propagation. Metrics to emit. |\n| Task | Specific log statements with level and message. Trace propagation. |\n\n**Required fields in structured logs:** `timestamp`, `level`, `message`, `trace_id`, `span_id`, `service`.\n\n---\n\n## 8. Decision Rationale\n\n**Rule anchor:** Rule 24 (Execution Integrity)\n**KP anchor:** N\u002FA\n**Required at:** Epic (mandatory, ≥1 item), Story (mandatory, ≥1 item), Task (optional — `N\u002FA — \u003Cshort reason>` accepted)\n\n### Micro-template (4-line format — MANDATORY for each decision)\n\n```markdown\n**Decisão:** \u003Cstatement of the decision made>\n**Motivo:** \u003Cwhy this option was chosen — technical or business constraint>\n**Alternativa descartada:** \u003Cwhat was rejected and why>\n**Consequência:** \u003Ctrade-off or future implication>\n```\n\n### Validation rules\n\n| Level | Rule |\n| :--- | :--- |\n| Epic | Section 8 MUST have ≥1 filled item using the 4-line micro-template. Placeholders (`{{...}}`), `TODO`, empty body → `RA9_RATIONALE_EMPTY` audit failure. |\n| Story | Same as Epic. |\n| Task | `N\u002FA — \u003Creason>` is accepted. If a design decision was made (retry count, lazy vs eager, algorithm choice), use the micro-template. |\n\n### Example (Story level)\n\n```markdown\n**Decisão:** Use `JpaPaymentRepository` as the outbound adapter instead of a custom JDBC template.\n**Motivo:** Spring Data JPA provides built-in transaction management and reduces boilerplate by 60% for this simple CRUD pattern.\n**Alternativa descartada:** Custom JDBC — rejected because it requires manual transaction handling and duplicates RowMapper code already present in 3 other adapters.\n**Consequência:** Binds the adapter to Spring Data JPA; future migration to reactive persistence requires adapter rewrite, not domain change.\n```\n\n---\n\n## 9. Dependências & File Footprint\n\n**Rule anchor:** Rule 14 (Project Scope)\n**KP anchor:** `knowledge\u002Fparallelism-heuristics.md`\n**Required at:** Epic (story index + dependency DAG), Story (task list + file footprint), Task (file list + `depends-on`)\n\n| Level | Required content |\n| :--- | :--- |\n| Epic | Story index table with dependency column. Implementation map reference. |\n| Story | Task list (Section 8). `## File Footprint` block for parallelism evaluation (Rule 04 EPIC-0041). |\n| Task | Explicit file list (`write:` \u002F `read:` \u002F `regen:`). `Dependencies` field (other task IDs or `—`). |\n\n### File Footprint format (Story level — RULE-004 EPIC-0041)\n\n```markdown\n## File Footprint\n\nwrite:\n  - src\u002Fmain\u002Fjava\u002Fdev\u002Fiadev\u002Fdomain\u002Fpayment\u002Fmodel\u002FPaymentOrder.java\n  - src\u002Fmain\u002Fjava\u002Fdev\u002Fiadev\u002Fadapter\u002Finbound\u002Frest\u002FPaymentController.java\nread:\n  - src\u002Fmain\u002Fjava\u002Fdev\u002Fiadev\u002Fdomain\u002Fpayment\u002Fport\u002FPaymentRepository.java\nregen:\n  - src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002F.claude\u002Fskills\u002Fx-epic-create\u002FSKILL.md\n```\n\n---\n\n## Granularity Summary Table\n\n| Section | Epic depth | Story depth | Task depth |\n| :--- | :--- | :--- | :--- |\n| 1. Contexto & Escopo | Vision + boundaries (3-5 sentences) | User story + context (2-3 paragraphs) | Single objective (1 sentence) |\n| 2. Packages (Hexagonal) | Full catalog all 5 layers | Story-scoped packages | 1-3 specific files |\n| 3. Contratos & Endpoints | Endpoint summary list | Full request\u002Fresponse schema | Single handler signature |\n| 4. Materialização SOLID | Cross-cutting business rules table | Story rules (RULE-NNN refs) | SOLID constraints per method |\n| 5. Quality Gates | Global DoR\u002FDoD | Local DoR\u002FDoD + Gherkin | DoD checklist |\n| 6. Segurança | Global security policies | OWASP checks + auth requirements | Code-level security rules |\n| 7. Observabilidade | SLO\u002FSLI definitions | Logging + tracing requirements | Specific log statements |\n| 8. Decision Rationale | ≥1 item (mandatory) | ≥1 item (mandatory) | N\u002FA accepted |\n| 9. Dependências & File Footprint | Story index + DAG | Task list + File Footprint block | File list + depends-on |\n\n---\n\n## Rule ↔ Section Mapping\n\n| Rule | Section(s) | Enforcement |\n| :--- | :--- | :--- |\n| Rule 01 — Project Identity | 1. Contexto & Escopo | Story persona must match domain |\n| Rule 03 — Coding Standards | 3. Contratos, 4. SOLID | Hard limits (≤25 lines, ≤250 class) |\n| Rule 04 — Architecture | 2. Packages | Dependency direction mandatory |\n| Rule 05 — Quality Gates | 5. Quality Gates | Absolute coverage gate (95\u002F90) |\n| Rule 06 — Security | 6. Segurança | At least one control per user-input story |\n| Rule 07 — Operations | 7. Observabilidade | Structured logging fields required |\n| Rule 14 — Project Scope | 9. Dependências | File footprint block in stories |\n| Rule 24 — Execution Integrity | 8. Decision Rationale | 4-line micro-template mandatory |\n\n---\n\n## Audit Rules (RA9 CI enforcement — RULE-006 EPIC-0056)\n\n| Code | Applies to | Fails when |\n| :--- | :--- | :--- |\n| `RA9_SECTIONS_MISSING` | Epic, Story, Task | Any of the 9 `## N. \u003Cname>` headers absent |\n| `RA9_RATIONALE_EMPTY` | Epic, Story (NOT Task) | Section 8 present but body is empty, `{{...}}`, or `TODO` |\n| `RA9_PACKAGES_MISSING` | Epic, Story, Task | Section 2 present but all 5 layers marked `—` |\n\nEscape hatch: `\u003C!-- audit-exempt -->` on the line immediately before the artifact (rare, reviewed exceptions only).\n",{"name":5,"description":7,"context-budget":24,"user-invocable":20,"requires-capabilities":25},"medium",[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fplanning-standards-kp",1,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment","https:\u002F\u002Fgithub.com\u002Freview-bench","https:\u002F\u002Freview-bench.ai","An open benchmark for AI code review.","2026-10-27 06:56:37",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill planning-standards-kp",{"tool":41,"command":42},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill planning-standards-kp",{"tool":44,"command":45},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill planning-standards-kp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-fintech-pci\u002F.claude\u002Fskills\u002Fplanning-standards-kp\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M757M8J48TQ1Y3X25GSJBXAS","x-parallel-eval","Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan \u002F x-story-plan, applies the parallelism-heuristics knowledge pack (hard \u002F regen \u002F soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fx-parallel-eval\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M757M57XMR9546S69466HDWT","parallelism-heuristics","Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard \u002F regen \u002F soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fparallelism-heuristics\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M757M11SZ8P1VCQABT08QVYA","x-watch-pr-ci","Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-watch-pr-ci\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M757KW53K8KFPGADFB4PH949","x-validate-docs","Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared\u002Fauto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-validate-docs\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M757KQZHSA10MKC0CR571D60","x-update-system-architecture","Incrementally updates docs\u002Farchitecture\u002Fsystem.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component\u002Fintegration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-system-architecture\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M757KKBT5Q1SVF8DMJBVF46M","x-update-architecture","Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FSKILL.md",[],[]]