verdicspec 0.2.2 → 0.2.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (80) hide show
  1. package/.agents/agents/architect.md +7 -7
  2. package/.agents/agents/debugger.md +8 -8
  3. package/.agents/agents/explorer.md +11 -11
  4. package/.agents/agents/implementer.md +9 -9
  5. package/.agents/agents/observability-engineer.md +6 -6
  6. package/.agents/agents/planner.md +7 -7
  7. package/.agents/agents/pr-creator.md +6 -6
  8. package/.agents/agents/releaser.md +6 -6
  9. package/.agents/agents/reviewer.md +6 -6
  10. package/.agents/agents/security-reviewer.md +11 -6
  11. package/.agents/agents/specifier.md +9 -9
  12. package/.agents/agents/spike-engineer.md +7 -7
  13. package/.agents/agents/tester.md +7 -7
  14. package/.agents/agents/verifier.md +6 -6
  15. package/.agents/rules/agent-skill-routing.md +23 -23
  16. package/.agents/skills/practices/security/SKILL.md +105 -3
  17. package/.agents/skills/practices/security/checklist.md +40 -0
  18. package/.claude/agents/architect.md +7 -7
  19. package/.claude/agents/debugger.md +8 -8
  20. package/.claude/agents/explorer.md +11 -11
  21. package/.claude/agents/implementer.md +9 -9
  22. package/.claude/agents/observability-engineer.md +6 -6
  23. package/.claude/agents/planner.md +7 -7
  24. package/.claude/agents/pr-creator.md +6 -6
  25. package/.claude/agents/releaser.md +6 -6
  26. package/.claude/agents/reviewer.md +6 -6
  27. package/.claude/agents/security-reviewer.md +11 -6
  28. package/.claude/agents/specifier.md +9 -9
  29. package/.claude/agents/spike-engineer.md +7 -7
  30. package/.claude/agents/tester.md +7 -7
  31. package/.claude/agents/verifier.md +6 -6
  32. package/.claude/rules/agent-skill-routing.md +23 -23
  33. package/.claude/skills/practices/security/SKILL.md +105 -3
  34. package/.claude/skills/practices/security/checklist.md +40 -0
  35. package/.cursor/agents/architect.md +7 -7
  36. package/.cursor/agents/debugger.md +8 -8
  37. package/.cursor/agents/explorer.md +11 -11
  38. package/.cursor/agents/implementer.md +9 -9
  39. package/.cursor/agents/observability-engineer.md +6 -6
  40. package/.cursor/agents/planner.md +7 -7
  41. package/.cursor/agents/pr-creator.md +6 -6
  42. package/.cursor/agents/releaser.md +6 -6
  43. package/.cursor/agents/reviewer.md +6 -6
  44. package/.cursor/agents/security-reviewer.md +11 -6
  45. package/.cursor/agents/specifier.md +9 -9
  46. package/.cursor/agents/spike-engineer.md +7 -7
  47. package/.cursor/agents/tester.md +7 -7
  48. package/.cursor/agents/verifier.md +6 -6
  49. package/.cursor/rules/agent-skill-routing.mdc +23 -23
  50. package/.cursor/skills/practices/security/SKILL.md +105 -3
  51. package/.cursor/skills/practices/security/checklist.md +40 -0
  52. package/LICENSE +21 -0
  53. package/README.md +1 -1
  54. package/agents/architect.md +7 -7
  55. package/agents/debugger.md +8 -8
  56. package/agents/explorer.md +11 -11
  57. package/agents/implementer.md +9 -9
  58. package/agents/observability-engineer.md +6 -6
  59. package/agents/planner.md +7 -7
  60. package/agents/pr-creator.md +6 -6
  61. package/agents/releaser.md +6 -6
  62. package/agents/reviewer.md +6 -6
  63. package/agents/security-reviewer.md +11 -6
  64. package/agents/specifier.md +9 -9
  65. package/agents/spike-engineer.md +7 -7
  66. package/agents/tester.md +7 -7
  67. package/agents/verifier.md +6 -6
  68. package/bin/verdicspec.mjs +2 -5
  69. package/docs/portable-adapters.md +0 -3
  70. package/docs/tool-support.md +4 -8
  71. package/package.json +1 -4
  72. package/skills/practices/security/SKILL.md +105 -3
  73. package/skills/practices/security/checklist.md +40 -0
  74. package/templates/threat-model.md +27 -6
  75. package/.clinerules/verdicspec.md +0 -6
  76. package/.github/copilot-instructions.md +0 -6
  77. package/.github/workflows/ci.yml +0 -40
  78. package/.github/workflows/publish.yml +0 -32
  79. package/.github/workflows/release.yml +0 -104
  80. package/GEMINI.md +0 -6
@@ -1,11 +1,16 @@
1
1
  ---
2
2
  name: security-reviewer
3
- description: Revisa riscos de seguranca, privacidade e supply-chain. Use proativamente em mudancas sensiveis.
3
+ description: Review security, privacy, abuse, and supply-chain risks. Use proactively for sensitive changes (auth, secrets, multi-tenant, upload/URL, containers, CI).
4
4
  ---
5
5
 
6
- Voce e o agent `security-reviewer` do Verdicspec.
6
+ You are the Verdicspec `security-reviewer` agent.
7
7
 
8
- Quando invocado:
9
- 1. Leia e siga `skills/practices/security/SKILL.md`.
10
- 2. Bloqueie secrets e acesso indevido.
11
- 3. Registre riscos e mitigacoes.
8
+ When invoked:
9
+ 1. Read and follow `skills/practices/security/SKILL.md` (and `checklist.md` when useful).
10
+ 2. Identify assets, trust boundaries, and attack surface for the change.
11
+ 3. Review the diff and adjacent code against the checklist (injection, authZ, secrets, SSRF, XSS, path traversal, deps, container/IaC, logs).
12
+ 4. Block secrets and unauthorized access: if something leaked, require rotation/revocation — deleting from code is not enough.
13
+ 5. For high-risk changes, produce a threat model from `templates/threat-model.md` under `.verdicspec/reports/`.
14
+ 6. Report findings by severity with impact, mitigation, residual risk, and what was (or was not) verified.
15
+ 7. Do not invent SAST/SCA/DAST/secret-scan results; cite only what was executed.
16
+ 8. Do not run DAST/attacks against production or unauthorized environments.
@@ -1,14 +1,14 @@
1
1
  ---
2
2
  name: specifier
3
- description: Cria ou refina especificacao testavel antes de codar. Use proativamente em feature nova ou mudanca de comportamento.
3
+ description: Create or refine a testable specification before coding. Use proactively for new features or behavior changes.
4
4
  ---
5
5
 
6
- Voce e o agent `specifier` do Verdicspec.
6
+ You are the Verdicspec `specifier` agent.
7
7
 
8
- Quando invocado:
9
- 1. Leia e siga `skills/core/specification/SKILL.md`.
10
- 2. Se aplicavel, leia tambem `skills/core/requirements/SKILL.md`.
11
- 3. Defina intent, comportamento, constraints e acceptance criteria.
12
- 4. Use templates/feature-spec.md quando aplicavel.
13
- 5. Nao implemente codigo nesta etapa.
14
- 6. Peca aprovacao quando a mudanca for media/grande.
8
+ When invoked:
9
+ 1. Read and follow `skills/core/specification/SKILL.md`.
10
+ 2. When applicable, also read `skills/core/requirements/SKILL.md`.
11
+ 3. Define intent, behavior, constraints, and acceptance criteria.
12
+ 4. Use `templates/feature-spec.md` when applicable.
13
+ 5. Do not implement code in this step.
14
+ 6. Ask for approval when the change is medium or large.
@@ -1,12 +1,12 @@
1
1
  ---
2
2
  name: spike-engineer
3
- description: Responde pergunta tecnica com experimento limitado e evidencia. Use proativamente em incerteza tecnica.
3
+ description: Answer a technical question with a bounded experiment and evidence. Use proactively for technical uncertainty.
4
4
  ---
5
5
 
6
- Voce e o agent `spike-engineer` do Verdicspec.
6
+ You are the Verdicspec `spike-engineer` agent.
7
7
 
8
- Quando invocado:
9
- 1. Leia e siga `skills/core/spike/SKILL.md`.
10
- 2. Limite tempo e escopo.
11
- 3. Registre evidencia e conclusao.
12
- 4. Nao trate spike como codigo de producao.
8
+ When invoked:
9
+ 1. Read and follow `skills/core/spike/SKILL.md`.
10
+ 2. Limit time and scope.
11
+ 3. Record evidence and the conclusion.
12
+ 4. Do not treat spike code as production code.
package/agents/tester.md CHANGED
@@ -1,12 +1,12 @@
1
1
  ---
2
2
  name: tester
3
- description: Desenha e executa testes a partir do comportamento. Use proativamente em logica testavel e regressao.
3
+ description: Design and run tests from behavior. Use proactively for testable logic and regressions.
4
4
  ---
5
5
 
6
- Voce e o agent `tester` do Verdicspec.
6
+ You are the Verdicspec `tester` agent.
7
7
 
8
- Quando invocado:
9
- 1. Leia e siga `skills/practices/testing/SKILL.md`.
10
- 2. Derive testes dos acceptance criteria.
11
- 3. Execute e reporte evidencia real.
12
- 4. Nao declare cobertura sem rodar.
8
+ When invoked:
9
+ 1. Read and follow `skills/practices/testing/SKILL.md`.
10
+ 2. Derive tests from acceptance criteria.
11
+ 3. Execute and report real evidence.
12
+ 4. Do not claim coverage without running tests.
@@ -1,11 +1,11 @@
1
1
  ---
2
2
  name: verifier
3
- description: Gate final: mapeia acceptance criteria para evidencia executada. Use sempre antes de declarar pronto, commit ou PR.
3
+ description: Final gate — map acceptance criteria to executed evidence. Always use before declaring done, committing, or opening a PR.
4
4
  ---
5
5
 
6
- Voce e o agent `verifier` do Verdicspec.
6
+ You are the Verdicspec `verifier` agent.
7
7
 
8
- Quando invocado:
9
- 1. Leia e siga `skills/practices/verification/SKILL.md`.
10
- 2. Separe evidenciado vs assumido.
11
- 3. Nao declare sucesso sem evidencia fresca.
8
+ When invoked:
9
+ 1. Read and follow `skills/practices/verification/SKILL.md`.
10
+ 2. Separate evidenced from assumed.
11
+ 3. Do not declare success without fresh evidence.
@@ -20,17 +20,14 @@ const adapters = {
20
20
  codex: ['AGENTS.md', '.agents-bundle'],
21
21
  antigravity: ['AGENTS.md', '.agents-bundle'],
22
22
  claude: ['CLAUDE.md', '.claude-bundle'],
23
- cursor: ['.cursor'],
24
- copilot: ['.github/copilot-instructions.md', '.agents-bundle'],
25
- gemini: ['GEMINI.md'],
26
- cline: ['.clinerules']
23
+ cursor: ['.cursor']
27
24
  };
28
25
 
29
26
  function usage() {
30
27
  console.log(`Verdicspec CLI
31
28
 
32
29
  Usage:
33
- verdicspec init [directory] [--tool all|codex|claude|cursor|antigravity|copilot|gemini|cline] [--force]
30
+ verdicspec init [directory] [--tool all|codex|claude|cursor|antigravity] [--force]
34
31
  verdicspec validate
35
32
  verdicspec list
36
33
  verdicspec doctor [directory]
@@ -20,9 +20,6 @@ Verdicspec has one canonical source and thin tool adapters.
20
20
  | Claude Code | `CLAUDE.md` + `.claude/rules/` | `.claude/agents/` | `.claude/skills/` |
21
21
  | OpenAI Codex | `AGENTS.md` | `.agents/agents/` | `.agents/skills/` or `skills/` |
22
22
  | Antigravity | `.agents/rules/` + `AGENTS.md` | `.agents/agents/` | `.agents/skills/` |
23
- | GitHub Copilot | `.github/copilot-instructions.md` | — | `.agents/skills/` |
24
- | Gemini CLI | `GEMINI.md` | — | points to canonical skills |
25
- | Cline | `.clinerules/verdicspec.md` | — | points to canonical skills |
26
23
 
27
24
  Install with:
28
25
 
@@ -12,13 +12,9 @@ ChatGPT or the GPT API by itself does not automatically inspect a local reposito
12
12
 
13
13
  | Environment | Entry point | Level |
14
14
  |---|---|---|
15
- | OpenAI Codex / ChatGPT Codex | `AGENTS.md` | Native repository instructions |
16
- | GPT through another agent host | Host-specific adapter | Supported when the host loads the files |
17
- | Claude Code | `CLAUDE.md`, `.claude/skills/` | Native adapter and skills |
18
- | Cursor | `.cursor/rules/` | Native rules adapter |
19
- | GitHub Copilot | `.github/copilot-instructions.md`, `.agents/skills/` | Native instructions and skills |
20
- | Gemini CLI | `GEMINI.md` | Native context adapter |
21
- | Cline | `.clinerules/` | Native workspace rules adapter |
15
+ | OpenAI Codex / ChatGPT Codex | `AGENTS.md`, `.agents/` | Native repository instructions, agents, and skills |
16
+ | Claude Code | `CLAUDE.md`, `.claude/` | Native adapter, agents, and skills |
17
+ | Cursor | `.cursor/rules/`, `.cursor/agents/`, `.cursor/skills/` | Native rules, agents, and skills |
18
+ | Antigravity | `AGENTS.md`, `.agents/` | Native rules, agents, and skills |
22
19
 
23
20
  The portable contract is the same in every environment: read the repository contract, discover the project technology, select the workflow, load only the required skills, and report evidence.
24
-
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "verdicspec",
3
- "version": "0.2.2",
3
+ "version": "0.2.3",
4
4
  "description": "Portable specification-driven engineering method and skills for AI coding agents",
5
5
  "repository": {
6
6
  "type": "git",
@@ -23,10 +23,7 @@
23
23
  "files": [
24
24
  "AGENTS.md",
25
25
  "CLAUDE.md",
26
- "GEMINI.md",
27
- ".clinerules",
28
26
  ".cursor",
29
- ".github",
30
27
  ".verdicspec",
31
28
  ".agents",
32
29
  ".claude",
@@ -1,11 +1,113 @@
1
1
  ---
2
2
  name: security
3
- description: Identify and reduce security, privacy, abuse, and supply-chain risks in a software change.
3
+ description: Identify and reduce security, privacy, abuse, and supply-chain risks in a software change. Use for auth, secrets, injection, XSS, SSRF, containers, IaC, CI/CD, and threat modeling.
4
4
  ---
5
5
 
6
6
  # Security
7
7
 
8
- Consider trust boundaries, authentication, authorization, input handling, secrets, sensitive data, dependency risk, logging exposure, abuse cases, and failure behavior.
8
+ Apply security whenever a change touches trust boundaries, authentication, authorization, input/output handling, secrets, sensitive data, dependencies, containers/IaC, CI/CD, logging, or abuse cases.
9
9
 
10
- For high-risk changes, produce `.verdicspec/reports/<change-id>-threat-model.md` from `templates/threat-model.md`, with assets, actors, entry points, threats, mitigations, verification, and residual risk. Do not treat passing tests as proof that security risk is absent.
10
+ Passing functional tests is **not** proof that security risk is absent. Prefer shift-left checks and defense in depth: design → code → commit → build → package → deploy → operate.
11
11
 
12
+ ## Principles
13
+
14
+ - Fail closed; default deny; least privilege.
15
+ - Validate on the server; never trust the client.
16
+ - Secrets in the git history are compromised — rotate, do not only delete.
17
+ - No single control is enough (SAST ≠ SCA ≠ DAST ≠ human review).
18
+ - Security requirements belong in acceptance criteria for sensitive changes.
19
+
20
+ ## Review checklist
21
+
22
+ Work through the relevant items for the change. Skip categories with no exposure, and say what was out of scope.
23
+
24
+ ### 1. Design and trust boundaries
25
+
26
+ - Assets, actors, entry points, and trust boundaries identified.
27
+ - AuthN/AuthZ decisions explicit; admin/write paths not anonymous by accident.
28
+ - Sensitive data classified (credentials, PII, tokens, business data).
29
+ - Abuse cases considered (IDOR, privilege escalation, mass assignment, replay).
30
+
31
+ ### 2. Input, output, and injection
32
+
33
+ - All untrusted input validated (type, length, allowlist when possible).
34
+ - SQL/NoSQL/LDAP/OS commands use parameterized APIs — no string concatenation.
35
+ - Templates do not compile untrusted content (no SSTI).
36
+ - HTML/JS output escaped; avoid raw HTML sinks (`dangerouslySetInnerHTML`, `innerHTML`) for untrusted data.
37
+ - File paths resolved and confined to an allowlisted directory (no path traversal).
38
+ - URL/fetch destinations allowlisted when the server initiates outbound calls (SSRF); block private/link-local ranges; verify TLS.
39
+ - Deserialization uses safe loaders (`yaml.safe_load`, equivalent); reject unexpected shape/size.
40
+ - Dangerous sinks (`eval`, `shell=True`, dynamic code execution) absent or strictly justified.
41
+
42
+ ### 3. Authentication, sessions, and credentials
43
+
44
+ - No default/hardcoded credentials (`admin:admin`, embedded tokens).
45
+ - Secrets from environment/secret store; `.env` and keys gitignored.
46
+ - Session/cookie flags and CSRF considered when cookies are used.
47
+ - CORS is not treated as access control; origins restricted when credentials are involved.
48
+
49
+ ### 4. Secrets and repository hygiene
50
+
51
+ - No secrets in source, config committed by mistake, Docker layers, or CI logs.
52
+ - If a secret leaked: rotate/revoke first, then remove, then baseline historical findings if needed.
53
+ - Prefer secret scanning in pre-commit and CI; protect main branch and sensitive paths (`CODEOWNERS`).
54
+
55
+ ### 5. Supply chain (dependencies)
56
+
57
+ - Lockfiles present and used; versions pinned for reproducible installs.
58
+ - Known vulnerable packages checked (SCA); prefer maintained packages.
59
+ - New dependencies justified; watch typosquatting and abandoned packages.
60
+ - Prefer SBOM / advisory awareness for release-critical systems.
61
+
62
+ ### 6. Containers, IaC, and runtime
63
+
64
+ - Non-root user, minimal base image, no secrets in `ENV`/`COPY`.
65
+ - Healthcheck, dropped capabilities, read-only FS and resource limits when applicable.
66
+ - Do not publish databases/admin ports to untrusted networks.
67
+ - Debug mode and development servers off outside isolated local use.
68
+ - IaC reviewed for exposure, privilege, and secret embedding.
69
+
70
+ ### 7. Errors, logs, and operations
71
+
72
+ - Client errors are generic; detailed traces only in protected logs.
73
+ - Logs omit secrets, tokens, passwords, and unnecessary PII.
74
+ - Rate limits / size limits / timeouts on expensive or dangerous endpoints.
75
+ - Audit trail for sensitive mutations when repudiation matters.
76
+
77
+ ### 8. Pipeline and verification controls
78
+
79
+ Map available (or recommended) controls without inventing tool output:
80
+
81
+ | Layer | Looks at | Typical findings |
82
+ |---|---|---|
83
+ | Threat model | Design | Missing auth, exposed assets |
84
+ | Secret scan | Code + git history | Tokens, keys, passwords |
85
+ | SAST | Own source | Injection, XSS, insecure APIs |
86
+ | SCA | Third-party deps | CVEs, abandoned packages |
87
+ | Image / IaC scan | Image + infra files | Base CVEs, root container, open ports |
88
+ | DAST | Running app (non-prod) | Runtime injection, missing headers |
89
+ | Human review | Diff + context | Logic abuse, auth gaps scanners miss |
90
+
91
+ - Run or cite only checks that actually executed.
92
+ - DAST only against disposable/non-production environments; triage false positives before blocking.
93
+ - Prefer gradual enforcement: inform → clean backlog → then fail the pipeline.
94
+
95
+ ## High-risk changes
96
+
97
+ Produce `.verdicspec/reports/<change-id>-threat-model.md` from `templates/threat-model.md` when the change affects auth, multi-tenant data, payments, secrets, remote code/file/URL handling, public exposure, or privilege boundaries.
98
+
99
+ Include: assets, actors, entry points, STRIDE-oriented threats, mitigations, verification, residual risk, and a short treatment order (contain → eliminate injection → close indirect access → harden runtime → verify).
100
+
101
+ Useful references for depth (do not paste wholesale): OWASP Top 10 / ASVS / Cheat Sheets, CWE, NIST SSDF, SLSA.
102
+
103
+ ## Output
104
+
105
+ Report findings by severity (`Critical` / `High` / `Medium` / `Low` / `Info`) with:
106
+
107
+ - location (file/route/config),
108
+ - impact and likely abuse path,
109
+ - concrete mitigation,
110
+ - residual risk if unfixed,
111
+ - verification status (executed / not executed).
112
+
113
+ If no findings, state what was reviewed and what was **not** verified.
@@ -0,0 +1,40 @@
1
+ # Security checklist (quick)
2
+
3
+ Use during review. Mark N/A when the change has no exposure in that area.
4
+
5
+ ## Design
6
+
7
+ - [ ] Assets and trust boundaries identified
8
+ - [ ] AuthN/AuthZ explicit for write/admin paths
9
+ - [ ] Sensitive data classified
10
+ - [ ] Abuse cases considered (IDOR, privilege escalation)
11
+
12
+ ## Code
13
+
14
+ - [ ] Server-side validation of untrusted input
15
+ - [ ] Parameterized queries / safe APIs (no injection)
16
+ - [ ] Output encoding / no unsafe HTML sinks for untrusted data
17
+ - [ ] Path, SSRF, SSTI, unsafe deserialization controlled
18
+ - [ ] No `eval` / shell injection sinks
19
+
20
+ ## Secrets and auth
21
+
22
+ - [ ] No hardcoded or default credentials
23
+ - [ ] Secrets via env/secret store; `.env` gitignored
24
+ - [ ] Leaked secret rotated (not only deleted)
25
+ - [ ] CORS not used as access control
26
+
27
+ ## Supply chain and packaging
28
+
29
+ - [ ] Lockfiles present; vulnerable deps checked
30
+ - [ ] Container non-root / minimal image when applicable
31
+ - [ ] No secrets in image layers or CI logs
32
+ - [ ] Ports and privileges minimized
33
+
34
+ ## Verify and operate
35
+
36
+ - [ ] Errors generic to clients; details in protected logs
37
+ - [ ] Logs without secrets/PII
38
+ - [ ] Rate/size/timeouts on risky endpoints
39
+ - [ ] Security checks executed or explicitly marked not run
40
+ - [ ] Threat model written for high-risk changes
@@ -5,6 +5,7 @@
5
5
  - System or change:
6
6
  - Assets:
7
7
  - Trust boundaries:
8
+ - Data sensitivity:
8
9
  - Out of scope:
9
10
 
10
11
  ## Actors and entry points
@@ -13,19 +14,39 @@
13
14
  |---|---|---|---|
14
15
  | | | | |
15
16
 
16
- ## Threats
17
+ ## STRIDE threats
17
18
 
18
- | ID | Threat | Asset or boundary | Likelihood | Impact | Mitigation | Residual risk |
19
+ Classify each threat (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege).
20
+
21
+ | ID | Priority | STRIDE | Asset / flow | Scenario and impact | Mitigation | Residual risk |
19
22
  |---|---|---|---|---|---|---|
20
- | THR-001 | | | Low / Medium / High | Low / Medium / High | | |
23
+ | THR-001 | Critical / High / Medium / Low | | | | | |
21
24
 
22
25
  ## Security requirements
23
26
 
24
27
  - SEC-001:
25
28
 
29
+ ## Treatment order
30
+
31
+ 1. Contain exposure (rotate secrets, restrict network/access).
32
+ 2. Eliminate injection / unsafe execution.
33
+ 3. Close indirect access (SSRF, path traversal, open admin paths).
34
+ 4. Protect users and operations (authZ, encoding, audit).
35
+ 5. Harden runtime (debug off, least privilege, limits).
36
+ 6. Verify with negative tests and available scanners.
37
+
26
38
  ## Verification
27
39
 
28
- - Test or check:
29
- - Manual review:
30
- - Remaining uncertainty:
40
+ | Check | Executed? | Evidence / result |
41
+ |---|---|---|
42
+ | Secret scan | Yes / No | |
43
+ | SAST | Yes / No | |
44
+ | SCA | Yes / No | |
45
+ | Image / IaC scan | Yes / No | |
46
+ | DAST (non-prod only) | Yes / No | |
47
+ | Manual review | Yes / No | |
48
+ | Negative tests | Yes / No | |
49
+
50
+ ## Remaining uncertainty
31
51
 
52
+ -
@@ -1,6 +0,0 @@
1
- ---
2
- description: Apply the Verdicspec to software engineering work.
3
- ---
4
-
5
- Read `AGENTS.md` before working. Use the smallest applicable skill from `skills/` and the relevant technology pack from `technology-packs/`. Keep requirements, implementation, and verification evidence explicit.
6
-
@@ -1,6 +0,0 @@
1
- # Verdicspec instructions
2
-
3
- Follow the repository contract in [`AGENTS.md`](../AGENTS.md).
4
-
5
- Before changing code, load the relevant skill from `skills/` and the matching technology pack from `technology-packs/` when applicable.
6
-
@@ -1,40 +0,0 @@
1
- name: CI
2
-
3
- on:
4
- push:
5
- branches: [main]
6
- pull_request:
7
-
8
- permissions:
9
- contents: read
10
-
11
- jobs:
12
- validate:
13
- runs-on: ubuntu-latest
14
- steps:
15
- - name: Checkout
16
- uses: actions/checkout@v6
17
-
18
- - name: Setup Node.js
19
- uses: actions/setup-node@v6
20
- with:
21
- node-version: 24
22
- cache: npm
23
-
24
- - name: Install dependencies
25
- run: npm ci
26
-
27
- - name: Validate package
28
- run: npm run validate
29
-
30
- - name: Run CLI tests
31
- run: npm test
32
-
33
- - name: Test CLI help and package listing
34
- run: |
35
- node bin/verdicspec.mjs help
36
- node bin/verdicspec.mjs list
37
-
38
- - name: Check package contents
39
- run: npm pack --dry-run
40
-
@@ -1,32 +0,0 @@
1
- name: Manual npm publish
2
-
3
- on:
4
- workflow_dispatch:
5
-
6
- permissions:
7
- contents: read
8
- id-token: write
9
-
10
- jobs:
11
- publish:
12
- runs-on: ubuntu-latest
13
- environment: npm
14
- steps:
15
- - name: Checkout
16
- uses: actions/checkout@v6
17
-
18
- - name: Setup Node.js
19
- uses: actions/setup-node@v6
20
- with:
21
- node-version: 24
22
- registry-url: https://registry.npmjs.org
23
- package-manager-cache: false
24
-
25
- - name: Install dependencies
26
- run: npm ci
27
-
28
- - name: Validate package
29
- run: npm run validate
30
-
31
- - name: Publish with npm trusted publishing
32
- run: npm publish
@@ -1,104 +0,0 @@
1
- name: Release on main
2
-
3
- on:
4
- push:
5
- branches: [main]
6
- paths:
7
- - 'AGENTS.md'
8
- - 'CLAUDE.md'
9
- - 'GEMINI.md'
10
- - 'README.md'
11
- - '.clinerules/**'
12
- - '.cursor/**'
13
- - '.github/copilot-instructions.md'
14
- - '.verdicspec/**'
15
- - 'bin/**'
16
- - 'commands/**'
17
- - 'docs/**'
18
- - 'skills/**'
19
- - 'technology-packs/**'
20
- - 'templates/**'
21
- - 'package.json'
22
- - 'package-lock.json'
23
-
24
- permissions:
25
- contents: write
26
-
27
- concurrency:
28
- group: release-on-main
29
- cancel-in-progress: false
30
-
31
- jobs:
32
- release:
33
- if: github.actor != 'github-actions[bot]' && !contains(github.event.head_commit.message, '[skip release]')
34
- runs-on: ubuntu-latest
35
- environment: npm
36
- steps:
37
- - name: Checkout
38
- uses: actions/checkout@v6
39
- with:
40
- fetch-depth: 0
41
-
42
- - name: Setup Node.js
43
- uses: actions/setup-node@v6
44
- with:
45
- node-version: 24
46
- registry-url: https://registry.npmjs.org
47
- package-manager-cache: false
48
-
49
- - name: Install dependencies
50
- run: npm ci
51
-
52
- - name: Validate package
53
- run: npm run validate
54
-
55
- - name: Run tests
56
- run: npm test
57
-
58
- - name: Increment patch version
59
- id: version
60
- shell: bash
61
- run: |
62
- npm version patch --no-git-tag-version
63
- VERSION="$(node -p "require('./package.json').version")"
64
- echo "version=$VERSION" >> "$GITHUB_OUTPUT"
65
-
66
- - name: Publish package
67
- env:
68
- NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
69
- run: npm publish
70
-
71
- - name: Create release commit and tag
72
- env:
73
- VERSION: ${{ steps.version.outputs.version }}
74
- run: |
75
- git config user.name "github-actions[bot]"
76
- git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
77
- git add package.json package-lock.json
78
- git commit -m "chore(release): v${VERSION}"
79
- git tag --annotate "v${VERSION}" --message "Release v${VERSION}"
80
- git push origin HEAD:main
81
- git push origin "v${VERSION}"
82
-
83
- - name: Create GitHub Release
84
- env:
85
- GH_TOKEN: ${{ github.token }}
86
- GH_REPOSITORY: ${{ github.repository }}
87
- VERSION: ${{ steps.version.outputs.version }}
88
- run: |
89
- TAG="v${VERSION}"
90
- for attempt in 1 2 3 4 5 6; do
91
- if gh api "repos/${GH_REPOSITORY}/git/ref/tags/${TAG}" > /dev/null 2>&1; then
92
- break
93
- fi
94
- if [ "$attempt" -eq 6 ]; then
95
- echo "Tag ${TAG} was not visible through the GitHub API after pushing it."
96
- exit 1
97
- fi
98
- sleep 2
99
- done
100
- gh api --method POST "repos/${GH_REPOSITORY}/releases" \
101
- -f "tag_name=${TAG}" \
102
- -f "target_commitish=${GITHUB_SHA}" \
103
- -f "name=${TAG}" \
104
- -F generate_release_notes=true
package/GEMINI.md DELETED
@@ -1,6 +0,0 @@
1
- # Verdicspec
2
-
3
- Read and follow the repository contract in [AGENTS.md](AGENTS.md).
4
-
5
- Canonical skills are under skills/. Named agents are under gents/ (also mirrored for Cursor/Claude/Codex/Antigravity).
6
- Load only the skill relevant to the current task.