devspec 0.1.0__py3-none-any.whl

devspec_installer/payload/devspec/work-items/_template/clarify.md

@@ -0,0 +1,28 @@
+# Clarification Record
+
+Use this artifact only for blocking ambiguity resolution. Keep resumability, handoff, and next action in `Resume State`. Keep active and resolved blockers in `Clarification Log`. Do not duplicate intake or finalization details; reference the impacted artifact and section instead.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | clarify |
+| Current command | `/devspec.clarify` |
+| Current agent | devspec.clarify |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | active blocker ID or none |
+| Recommended option | active blocker option and reason or none |
+| Resume command | `/devspec.clarify` |
+| Resume notes | |
+| Updated | |
+
+## Clarification Log
+
+Use one row per blocker. Keep at most one row with `open` status; resolved, superseded, and withdrawn rows are the history. When no blocker is active, set `Pending user question` in `Resume State` to `none` and use `Next required action` for the handoff target. Open blockers must preserve the structured question intent, exact option labels, `Custom Answer`, and the recommended option with its reason.
+
+| ID | Status | Source artifact | Blocking gap | Question | Options | Recommended option and reason | User answer | Impacted artifacts | Updated |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| CLAR-001 | open, resolved, superseded, withdrawn | `story.md`, `finalize.md`, user input, or other source |  |  | intent; option labels including `Custom Answer` |  |  |  |  |

devspec_installer/payload/devspec/work-items/_template/decisions.md

@@ -0,0 +1,9 @@
+# Work-Item Decisions
+
+Use this artifact as the single work-item decision log. Record choices that affect scope, implementation, validation, rollout, or handoff. Keep intake context in `story.md`, readiness details in `finalize.md`, and durable cross-work-item architecture decisions in ADR files created under `devspec/architecture/decisions/` when needed; link those artifacts here instead of duplicating them.
+
+## Work-Item Decision Log
+
+| ID | Status | Decision | Rationale | Impact | Source or related artifacts | Updated |
+| --- | --- | --- | --- | --- | --- | --- |
+| DEC-001 | proposed, accepted, rejected, superseded |  |  |  |  |  |

devspec_installer/payload/devspec/work-items/_template/diagrams.md

@@ -0,0 +1,42 @@
+# Work-Item Diagrams
+
+Use this file only for explicit or clearly temporary work-item diagrams, such as a one-off bug reproduction flow, migration path, security incident or threat flow, temporary implementation plan, or experiment.
+
+Reusable process flows, feature workflows, module workflows, user journeys, sequences, and state diagrams should live under `devspec/architecture/diagrams/` and be referenced from the work item.
+
+Do not keep a separate diagram index or status here. `devspec/architecture/artifact-queue.md` owns diagram status from `devspec/glossary.md#artifact-status-values`. This file owns only temporary work-item-specific diagram content and the resume state needed to continue the diagram command.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | diagram |
+| Current command | `/devspec.diagram` |
+| Current agent | devspec.diagram |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | `/devspec.diagram` |
+| Resume notes | |
+| Updated | |
+
+## Diagram Content
+
+### DIA-001 - <subject>
+
+| Field | Value |
+| --- | --- |
+| Type | |
+| Subject | |
+| Queue source | `devspec/architecture/artifact-queue.md` |
+| Evidence sources | |
+| Confidence | observed, high-confidence, low-confidence |
+| Assumptions | none or listed below |
+| Notes | |
+
+```mermaid
+flowchart TD
+```

devspec_installer/payload/devspec/work-items/_template/finalize.md

@@ -0,0 +1,65 @@
+# Implementation Readiness Brief
+
+Use this artifact as the implementation readiness brief. Keep only details that affect readiness, implementation scope, task planning, validation, delivery risk, or handoff. Put lifecycle recovery in `Resume State`, readiness gating in `Readiness Assessment`, implementation facts in `Implementation Brief`, and proof expectations in `Validation Plan`.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | finalize |
+| Current command | `/devspec.finalize` |
+| Current agent | devspec.finalize |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | `/devspec.finalize` |
+| Resume notes | |
+| Updated | |
+
+## Readiness Assessment
+
+| Field | Value |
+| --- | --- |
+| Type | feature, bug, security-vulnerability |
+| Severity | bugs and security vulnerabilities only |
+| Priority | features should record priority |
+| Status | See `devspec/glossary.md#readiness-status-values`; use only `ready` or `not ready` for the overall decision |
+| Blocking gates | gate IDs or none |
+| Next action | `/devspec.tasks` when ready; `/devspec.clarify` or required foundation update when not ready |
+| Decision note | |
+| Decision inputs | `story.md`, `clarify.md`, accepted `decisions.md` records, `devspec/foundation/rules.md` |
+
+Use readiness gates only for checks that decide whether task planning may proceed. Record the missing fact or blocking action here; record implementation content in `Implementation Brief`.
+
+| ID | Check | Evidence source | Ready condition | Status | Blocking action |
+| --- | --- | --- | --- | --- | --- |
+| RG-001 | Scope boundary | Implementation Brief | In-scope and out-of-scope boundaries are explicit and do not expand the work item. | See `devspec/glossary.md#readiness-status-values` | |
+| RG-002 | Acceptance criteria | Implementation Brief | Criteria are observable or testable enough for task planning and validation. | See `devspec/glossary.md#readiness-status-values` | |
+| RG-003 | Dependencies and repository readiness | Implementation Brief; `devspec/foundation/codebase-structure.md` | Dependencies are captured and required repository configuration or access is confirmed or not applicable. | See `devspec/glossary.md#readiness-status-values` | |
+| RG-004 | Type-specific facts | Implementation Brief; `devspec/foundation/rules.md` | Feature priority, bug facts, or security-vulnerability facts required by project rules are captured or explicitly blocked. | See `devspec/glossary.md#readiness-status-values` | |
+| RG-005 | Validation and delivery risk | Implementation Brief; Validation Plan | Validation expectations and material delivery risks are known enough to plan tasks, or marked not applicable. | See `devspec/glossary.md#readiness-status-values` | |
+
+## Implementation Brief
+
+Use this as the single task-planning input table. Include only facts that affect scope, acceptance criteria, task decomposition, repository readiness, type-specific requirements, delivery risk, or handoff. For multi-repo work, summarize readiness here and keep local paths and access requirement values in `devspec/foundation/codebase-structure.md`. Put validation methods in `Validation Plan`.
+
+| Type | ID | Item | Source | Task-planning or delivery effect | Status |
+| --- | --- | --- | --- | --- | --- |
+| Scope: in | SCOPE-IN-001 | <implementation-boundary> | <intake-clarification-decision-or-user-input> | Tasks may be created only for this work. | confirmed |
+| Scope: out | SCOPE-OUT-001 | <explicit-non-goal> | <intake-clarification-decision-or-user-input> | Tasks must not be created for this work. | confirmed |
+| Acceptance criterion | AC-001 | <observable-outcome> | <intake-clarification-decision-or-user-input> | Drives implementation tasks and validation coverage. | pending |
+| Planning input | PI-001 | <assumption-constraint-dependency-or-target-area> | <foundation-intake-clarification-decision-or-discovery-source> | <how tasks should account for it> | pending |
+| Repository readiness | MR-001 | <required-repositories-and-access-confirmation-summary-or-not-applicable> | `devspec/foundation/codebase-structure.md` | Missing or blocked repository readiness prevents task planning. | pending |
+| Type-specific requirement | TS-001 | <bug-security-or-rule-required-fact> | <intake-clarification-decision-or-rule-source> | Required for task planning, validation, or release handling. | pending |
+| Risk or follow-up | RISK-001 | <risk-mitigation-backport-release-note-advisory-or-handoff-item> | <intake-clarification-decision-or-discovery-source> | <delivery-or-handoff-effect> | open |
+
+## Validation Plan
+
+Record how acceptance criteria, type-specific requirements, and material risks should be validated.
+
+| ID | Covers | Method or evidence | Expected signal | Status |
+| --- | --- | --- | --- | --- |
+| VP-001 | AC-001 | <test-command-review-or-manual-check> | <passing-signal> | pending |

devspec_installer/payload/devspec/work-items/_template/implement.md

@@ -0,0 +1,63 @@
+# Implementation Record
+
+Use this artifact for recovery, audit, and handoff during implementation. Keep lifecycle recovery in `Resume State`, per-task progress in `Implementation Task Ledger`, changed files and validation evidence in `Implementation Evidence`, and attempt history in `Implementation Execution Log`. Omit optional evidence rows with no entries.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | implement |
+| Current command | `/devspec.implement` |
+| Current agent | devspec.implement-task |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | `/devspec.implement` |
+| Resume notes | |
+| Updated | |
+
+## Implementation Task Ledger
+
+Use this as the single recovery view for implementation progress, current task, last safe checkpoint, and next handoff. Keep one row per task from `tasks.md`.
+
+| Field | Value |
+| --- | --- |
+| Overall status | See `devspec/glossary.md#task-status-values` |
+| Completed count | |
+| Pending count | |
+| Skipped count | |
+| Current task | |
+| Last completed task | |
+| Last confirmation outcome | proceed, continue, pause, skip, custom |
+| Known good state | |
+| Roll-forward notes | |
+| Completion note | |
+
+| Task | Target repository | Target area | Depends on | Status | Attempt count | Last checkpoint | Validation last run | Next action |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| T-001 |  |  |  | pending | 0 |  |  | |
+
+## Implementation Evidence
+
+Record only evidence that exists. Use this section for repository access checks, changed files, validation results, type-specific handling, residual risks, follow-ups, and review/audit snippets. Repository path and access requirement source is `devspec/foundation/codebase-structure.md`; type-specific rule source is `devspec/foundation/rules.md`.
+
+| Type | Applies to | Item | Evidence or notes | Status |
+| --- | --- | --- | --- | --- |
+| Repository access | <repository-name> | <access-requirement-and-status> | <confirmation-or-blocker-notes> | confirmed, missing, blocked |
+| Changed file | <task-id> | <path> | <change-summary-and-validation> | modified |
+| Validation | <task-id-or-scope> | <command-or-method> | <result-or-expected-signal> | pending, passed, failed, skipped |
+| Type-specific handling | <bug-security-or-rule> | <handling-note> | <rule-source-or-audit-note> | pending, complete |
+| Risk or follow-up | <task-id-or-work-item> | <risk-or-follow-up> | <owner-or-next-action> | open, pending, complete |
+| Review snippet | <task-id-or-file> | <before-after-or-audit-summary> | <why-useful-for-review> | recorded |
+| Token telemetry | <run-or-task> | before, after, unavailable | <usage-summary-or-unavailable-reason> | recorded |
+
+## Implementation Execution Log
+
+Record one row per task attempt, validation run, blocker, retry escalation, pause, skip, completion, or handoff. Failed methods, retry conditions, and next safer methods belong here.
+
+| Date | Task | Event | Attempt count | Status | Summary | Evidence refs | Blockers | Failed method and reason | Retry condition or next safer method | Confirmation or handoff |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+|  | T-001 | attempt, validation, blocker, retry-escalation, pause, skip, completion, handoff | 0 | pending |  |  |  |  |  |  |

devspec_installer/payload/devspec/work-items/_template/meta.md

@@ -0,0 +1,63 @@
+# Work-Item Metadata
+
+Use this artifact as the work-item control record. Keep only the stable work-item record, routing index, and current workflow state. Put detailed intake content in `story.md`, work-item decisions in `decisions.md`, implementation readiness in `finalize.md`, and execution state in `tasks.md` or `implement.md`.
+
+## Work-Item Record
+
+Use this section for durable identity, classification, intake provenance, ownership, dates, and links.
+
+| Field | Value |
+| --- | --- |
+| Title | |
+| Folder name | |
+| Naming status | valid, needs-confirmation, legacy |
+| Type | feature, bug, security-vulnerability |
+| Severity | low, medium, high, critical, n/a for feature |
+| Priority | record for features when available |
+| Disclosure status | internal, coordinated, public, n/a |
+| Source resolution status | See `devspec/glossary.md#source-resolution-status-values` |
+| Source system | |
+| Identifier | |
+| URL | |
+| Confirmation status | confirmed, rejected, pending, n/a |
+| Resolution notes | |
+| Owner | |
+| Reviewer | |
+| Created | |
+| Updated | |
+| Parent work item | |
+| Related ADRs | |
+| Related PRs or commits | |
+
+## Triage Index
+
+Use this section for routing and lookup only. Keep narrative impact, acceptance criteria, and dependency details in `story.md`.
+
+| Field | Value |
+| --- | --- |
+| Customer impact summary | |
+| Affected scope | |
+| Affected versions | |
+| Multi-repo dependency | yes, no |
+| Related repositories | repository names only |
+| Detail source | `story.md` |
+
+## Workflow State
+
+| Field | Value |
+| --- | --- |
+| Work item status | See `devspec/glossary.md#work-item-status-values` |
+| Readiness status | See `devspec/glossary.md#readiness-status-values` |
+| Review status | See `devspec/glossary.md#review-status-values` |
+| Current stage | |
+| Current command | |
+| Current agent | |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | |
+| Resume notes | |
+| Updated | |

devspec_installer/payload/devspec/work-items/_template/notes.md

@@ -0,0 +1,7 @@
+# Working Notes
+
+Use this artifact only for temporary working notes that do not yet belong in a canonical work-item artifact. Promote durable facts to `story.md`, decisions to `decisions.md`, clarification blockers to `clarify.md`, readiness details to `finalize.md`, tasks to `tasks.md`, implementation evidence to `implement.md`, and review findings to `review.md`.
+
+| Date | Note | Disposition |
+| --- | --- | --- |
+|  |  | keep, promoted, obsolete |

devspec_installer/payload/devspec/work-items/_template/review.md

@@ -0,0 +1,41 @@
+# Review Record
+
+Use this artifact for review outcome, actionable findings, and handoff. Keep lifecycle recovery in `Resume State`, overall review judgment and non-actionable notes in `Review Outcome`, and required changes or tracked gaps in `Review Findings`.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | review |
+| Current command | `/devspec.review` |
+| Current agent | devspec.review |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | `/devspec.review` |
+| Resume notes | |
+| Updated | |
+
+## Review Outcome
+
+| Field | Value |
+| --- | --- |
+| Status | See `devspec/glossary.md#review-status-values` |
+| Reviewer | |
+| Date | |
+| Summary | |
+| Finalized scope alignment | aligned, drift found, not reviewed |
+| Validation coverage | complete, gaps found, not reviewed |
+| Type-specific review notes | bug/security/rule notes or n/a |
+| Follow-up summary | |
+
+## Review Findings
+
+Record required changes, validation gaps, missing tests, scope drift, security risks, regressions, and follow-ups here. Use `Status` values such as `open`, `fixed`, `accepted-risk`, or `follow-up`.
+
+| ID | Severity | Category | Details | Required action | Evidence | Status |
+| --- | --- | --- | --- | --- | --- | --- |
+| F-001 | critical, high, medium, low | bug, regression, security, validation, test-gap, scope, maintainability, follow-up |  |  |  | open |

devspec_installer/payload/devspec/work-items/_template/story.md

@@ -0,0 +1,59 @@
+# Work-Item Intake
+
+Use this artifact for detailed work-item intake. Keep identity, classification, source provenance, and routing summaries in `meta.md`; keep work-item decisions in `decisions.md`; keep implementation-ready scope in `finalize.md`.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | story |
+| Current command | `/devspec.story` |
+| Current agent | devspec.story |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | `/devspec.story` |
+| Resume notes | |
+| Updated | |
+
+## Intake Source Record
+
+| Field | Value |
+| --- | --- |
+| External reference | |
+| Resolved summary shown | |
+| Confirmation basis | `devspec/foundation/provider-integrations.md` |
+| User confirmation | confirmed, rejected, pending |
+| Manual intake used | yes, no |
+| Manual description | |
+| Manual acceptance criteria | |
+
+## Work-Item Brief
+
+Use this section for the durable work-item narrative. Keep it concise but specific enough for clarification and finalization.
+
+| Field | Value |
+| --- | --- |
+| Problem | |
+| Intended outcome | |
+| User or customer impact | |
+| Affected components | |
+| Affected versions | |
+
+## Work-Item Details
+
+Use this table for facts that affect clarification, readiness, task planning, or validation. Keep repository paths and access requirements in `devspec/foundation/codebase-structure.md`; keep rule definitions in `devspec/foundation/rules.md`.
+
+| Type | ID | Item | Source | Status |
+| --- | --- | --- | --- | --- |
+| Acceptance criterion | AC-001 |  | confirmed, provider, manual, user | pending |
+| Assumption | ASM-001 |  | confirmed, inferred, user | open |
+| Constraint | CON-001 |  | foundation, intake, user | open |
+| Dependency | DEP-001 | <dependency-or-none> | intake, user, discovery | open |
+| Multi-repo dependency | DEP-REPO-001 | yes, no; related repositories: <repository-names-only> | confirmed, user | open |
+| Type-specific note | TS-001 | <bug-or-security-note>; rule source: `devspec/foundation/rules.md` | intake, user, rule | open |
+| Risk | RISK-001 |  | intake, user, discovery | open |
+| Blocker | BLK-001 |  | intake, user, discovery | open |

devspec_installer/payload/devspec/work-items/_template/tasks.md

@@ -0,0 +1,38 @@
+# Implementation Task Plan
+
+Use this artifact as the executable implementation plan. Keep lifecycle recovery in `Resume State`, source references in `Planning Basis`, and all executable task details in `Implementation Tasks`. Each task should include target, dependency, impacted area, validation, and done condition.
+
+## Resume State
+
+| Field | Value |
+| --- | --- |
+| Current stage | tasks |
+| Current command | `/devspec.tasks` |
+| Current agent | devspec.tasks |
+| Run status | See `devspec/glossary.md#run-status-values` |
+| Current item | |
+| Last completed step | |
+| Next required action | |
+| Pending user question | |
+| Recommended option | |
+| Resume command | `/devspec.tasks` |
+| Resume notes | |
+| Updated | |
+
+## Planning Basis
+
+| Field | Value |
+| --- | --- |
+| Implementation brief source | `finalize.md#implementation-brief` |
+| Validation source | `finalize.md#validation-plan` |
+| Readiness source | `finalize.md#readiness-assessment` |
+| Access requirement source | `devspec/foundation/codebase-structure.md` |
+| Type-specific rule source | `devspec/foundation/rules.md` |
+
+## Implementation Tasks
+
+Use one row per executable checkpoint. Put likely files or areas, validation steps, and done criteria on the task that owns them. Keep validation commands or methods specific enough for `implement.md` to execute or record.
+
+| ID | Task | Target repository | Target area or files | Required access | Depends on | Validation | Done when | Status | Attempt count | Last checkpoint |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| T-001 | <developer-action> | <repository-name> | <path-module-or-area> | See `devspec/glossary.md#access-requirement-values` | <task-id-or-none> | <command-method-or-review-signal-and-expected-result> | <observable-completion-condition-and-evidence> | pending | 0 | |

devspec_installer/payload/packaging/devspec-profiles.json

@@ -0,0 +1,60 @@
+{
+  "version": 1,
+  "profiles": {
+    "core": {
+      "description": "Core devspec framework, Copilot reference prompts and agents, and shared instructions.",
+      "includes": [
+        "devspec/**",
+        ".github/prompts/**",
+        ".github/agents/**",
+        "AGENTS.md"
+      ]
+    },
+    "copilot": {
+      "description": "GitHub Copilot support, including bundled reusable skills.",
+      "extends": ["core"],
+      "includes": [
+        ".github/skills/**"
+      ]
+    },
+    "codex": {
+      "description": "OpenAI Codex support through AGENTS.md and adapter guidance.",
+      "extends": ["core"],
+      "includes": []
+    },
+    "cursor": {
+      "description": "Cursor project rules plus shared AGENTS.md fallback guidance.",
+      "extends": ["core"],
+      "includes": [
+        ".cursor/**"
+      ]
+    },
+    "claude": {
+      "description": "Claude Code project skills for devspec workflows.",
+      "extends": ["core"],
+      "includes": [
+        ".claude/**"
+      ]
+    },
+    "gemini": {
+      "description": "Gemini CLI context and native /devspec:* command wrappers.",
+      "extends": ["core"],
+      "includes": [
+        "GEMINI.md",
+        ".gemini/**"
+      ]
+    },
+    "antigravity": {
+      "description": "Google Antigravity workspace rule and skill wrappers.",
+      "extends": ["core"],
+      "includes": [
+        ".agents/**"
+      ]
+    },
+    "all": {
+      "description": "All supported devspec adapter files.",
+      "extends": ["copilot", "codex", "cursor", "claude", "gemini", "antigravity"],
+      "includes": []
+    }
+  }
+}