From 894466300ff716874fc37f12ca3d1d3e47776d97 Mon Sep 17 00:00:00 2001 From: Ahmed Darrazi Date: Sat, 10 Jan 2026 22:39:16 +0100 Subject: [PATCH] docs: deprecate .specify specs and update references --- .specify/README.md | 14 ++++++++++++++ .specify/plan.md | 6 +++++- .specify/research_t186.md | 6 +++++- .specify/spec.md | 6 +++++- .specify/tasks.md | 6 +++++- Agents.md | 8 ++++---- GEMINI.md | 8 ++++---- specs/001-rbac-onboarding/tasks.md | 2 +- specs/004-assignments-scope-tags/plan.md | 2 +- specs/008-apps-app-management/spec.md | 2 +- specs/010-admin-templates/spec.md | 2 +- 11 files changed, 46 insertions(+), 16 deletions(-) create mode 100644 .specify/README.md diff --git a/.specify/README.md b/.specify/README.md new file mode 100644 index 0000000..e56f177 --- /dev/null +++ b/.specify/README.md @@ -0,0 +1,14 @@ +# `.specify/` (Tooling) + +This folder contains **SpecKit tooling** (templates, scripts, constitution, etc.). + +## Important + +- **Do not** create new feature specs in `.specify/spec.md`, `.specify/plan.md`, `.specify/tasks.md`. +- Active feature specs live under `specs/-/`: + - `spec.md` + - `plan.md` + - `tasks.md` + - `checklists/requirements.md` + +The files `.specify/spec.md`, `.specify/plan.md`, `.specify/tasks.md` may exist as legacy references only. diff --git a/.specify/plan.md b/.specify/plan.md index eb4bfe3..3009945 100644 --- a/.specify/plan.md +++ b/.specify/plan.md @@ -1,4 +1,8 @@ -# Implementation Plan: TenantPilot v1 +# Implementation Plan: TenantPilot v1 (LEGACY / DEPRECATED) + +> DEPRECATED: Do not use `.specify/plan.md` for new work. +> Active feature plans live under `specs/-/plan.md` on `feat/-` branches. +> Legacy history lives under `spechistory/`. **Branch**: `dev` **Date**: 2026-01-03 diff --git a/.specify/research_t186.md b/.specify/research_t186.md index 7fb31c7..23773aa 100644 --- a/.specify/research_t186.md +++ b/.specify/research_t186.md @@ -1,4 +1,8 @@ -# Research T186 — settings_apply capability verification +# Research T186 — settings_apply capability verification (LEGACY / DEPRECATED) + +> DEPRECATED: Do not add new research notes under `.specify/`. +> Active feature research should live under `specs/-/`. +> Legacy history lives under `spechistory/`. Objective --------- diff --git a/.specify/spec.md b/.specify/spec.md index 227841a..0845759 100644 --- a/.specify/spec.md +++ b/.specify/spec.md @@ -1,4 +1,8 @@ -# Feature Specification: TenantPilot v1 +# Feature Specification: TenantPilot v1 (LEGACY / DEPRECATED) + +> DEPRECATED: Do not use `.specify/spec.md` for new work. +> Active feature specs live under `specs/-/spec.md` on `feat/-` branches. +> Legacy history lives under `spechistory/`. **Feature Branch**: `dev` **Created**: 2025-12-10 diff --git a/.specify/tasks.md b/.specify/tasks.md index 701dd6f..e9d6fa7 100644 --- a/.specify/tasks.md +++ b/.specify/tasks.md @@ -2,7 +2,11 @@ description: "Task list for TenantPilot v1 implementation" --- -# Tasks: TenantPilot v1 +# Tasks: TenantPilot v1 (LEGACY / DEPRECATED) + +> DEPRECATED: Do not use `.specify/tasks.md` for new work. +> Active feature task lists live under `specs/-/tasks.md` on `feat/-` branches. +> Legacy history lives under `spechistory/`. **Input**: Design documents from `.specify/spec.md` and `.specify/plan.md` **Prerequisites**: plan.md (complete), spec.md (complete) diff --git a/Agents.md b/Agents.md index 647a326..4dc089a 100644 --- a/Agents.md +++ b/Agents.md @@ -26,9 +26,9 @@ ## Scope Reference ## Workflow (Spec Kit) 1. Read `.specify/constitution.md` -2. For new work: create/update `.specify/spec.md` -3. Produce `.specify/plan.md` -4. Break into `.specify/tasks.md` +2. For new work: create/update `specs/-/spec.md` +3. Produce `specs/-/plan.md` +4. Break into `specs/-/tasks.md` 5. Implement changes in small PRs If requirements change during implementation, update spec/plan before continuing. @@ -270,7 +270,7 @@ ## Engineering Rules - Keep Microsoft Graph integration isolated behind a dedicated abstraction layer. - Use dependency injection and clear interfaces for Graph clients. - No breaking changes to data structures or API contracts without updating: - - `.specify/spec.md` + - `specs/-/spec.md` - migration notes - upgrade steps - If a TypeScript/JS tooling package exists, use strict typing rules there too. diff --git a/GEMINI.md b/GEMINI.md index 503d98a..d9e766e 100644 --- a/GEMINI.md +++ b/GEMINI.md @@ -26,9 +26,9 @@ ## Scope Reference ## Workflow (Spec Kit) 1. Read `.specify/constitution.md` -2. For new work: create/update `.specify/spec.md` -3. Produce `.specify/plan.md` -4. Break into `.specify/tasks.md` +2. For new work: create/update `specs/-/spec.md` +3. Produce `specs/-/plan.md` +4. Break into `specs/-/tasks.md` 5. Implement changes in small PRs If requirements change during implementation, update spec/plan before continuing. @@ -110,7 +110,7 @@ ## Engineering Rules - Keep Microsoft Graph integration isolated behind a dedicated abstraction layer. - Use dependency injection and clear interfaces for Graph clients. - No breaking changes to data structures or API contracts without updating: - - `.specify/spec.md` + - `specs/-/spec.md` - migration notes - upgrade steps - If a TypeScript/JS tooling package exists, use strict typing rules there too. diff --git a/specs/001-rbac-onboarding/tasks.md b/specs/001-rbac-onboarding/tasks.md index c00b9c9..911075f 100644 --- a/specs/001-rbac-onboarding/tasks.md +++ b/specs/001-rbac-onboarding/tasks.md @@ -4,7 +4,7 @@ # Tasks: TenantPilot v1 -**Input**: Design documents from `.specify/spec.md` and `.specify/plan.md` +**Input**: `specs/001-rbac-onboarding/spec.md` and `specs/001-rbac-onboarding/plan.md` **Prerequisites**: plan.md (complete), spec.md (complete) --- diff --git a/specs/004-assignments-scope-tags/plan.md b/specs/004-assignments-scope-tags/plan.md index 70416cd..c493528 100644 --- a/specs/004-assignments-scope-tags/plan.md +++ b/specs/004-assignments-scope-tags/plan.md @@ -323,7 +323,7 @@ ### Phase 10: Deployment & Documentation - Run migrations on staging - Verify no data loss - Test on production-like data volume -2. Update `.specify/spec.md` with implementation notes +2. Update `specs/004-assignments-scope-tags/spec.md` with implementation notes 3. Create migration guide for existing backups (no retroactive assignment capture) 4. Add monitoring alerts: - Assignment fetch failure rate > 10% diff --git a/specs/008-apps-app-management/spec.md b/specs/008-apps-app-management/spec.md index f32e66b..7c01e57 100644 --- a/specs/008-apps-app-management/spec.md +++ b/specs/008-apps-app-management/spec.md @@ -3,7 +3,7 @@ # Feature Specification: Apps (Mobile Apps) Metadata-Only + Assignments **Feature Branch**: `feat/008-apps-app-management` **Created**: 2025-12-29 **Status**: Draft -**Input**: `.specify/spec.md` (mobileApp scope) + `references/IntuneManagement-master/Documentation/AppTypes.json` (known app @odata.type values). +**Input**: `spechistory/spec.md` (legacy v1 scope) + `references/IntuneManagement-master/Documentation/AppTypes.json` (known app @odata.type values). ## Overview Add reliable **mobile app** (`mobileApp`) coverage for inventory, backup/version capture, and restore: diff --git a/specs/010-admin-templates/spec.md b/specs/010-admin-templates/spec.md index e9e11af..78b396c 100644 --- a/specs/010-admin-templates/spec.md +++ b/specs/010-admin-templates/spec.md @@ -3,7 +3,7 @@ # Feature Specification: Administrative Templates (Group Policy Configurations) **Feature Branch**: `feat/010-admin-templates` **Created**: 2025-12-29 **Status**: Draft -**Input**: `.specify/spec.md` (groupPolicyConfiguration scope), `references/IntuneManagement-master` (definitionValues/presentationValues pattern) +**Input**: `spechistory/spec.md` (legacy v1 scope), `references/IntuneManagement-master` (definitionValues/presentationValues pattern) ## Overview Add reliable coverage for **Administrative Templates** (`groupPolicyConfiguration`) in the existing inventory/backup/version/restore flows.