Prompt file imported from ZenRay/CursorTemplate (.cursor/commands/paradigm-adopt.md). Copyright stays with the author.

/paradigm-adopt — Adopt Paradigm Gradually

Name: paradigm-adopt
Author: ZenRay

Adopt CursorHarness engineering paradigm in an existing (brownfield) project.

Phase 1: Audit Current State

Analyze existing project:

Structure audit: Current directory layout
Tech stack detection: Language, framework
Existing conventions: Any current standards?
Git state: Branch, recent commits
Conflicts: What will need adaptation?

Phase 2: Module-by-Module Plan

Create phased adoption plan:

Phase	Module	Action	Confirm?
1	Core config	.cursor/, AGENTS.md, STATE.md	✅
2	Hooks	T1 (security) first	✅
3	Rules	Priority rules only	✅
4	Commands	Essential commands	✅
5	Docs	architecture.md, standards	✅
6	Full adoption	Remaining components	✅

Phase 3: Execute (Per Module)

For each module, user confirms before proceeding:

Module 1: Core Configuration

Copy without overwrite:

.cursor/ directory
AGENTS.md (adapt project name)
STATE.md (analyze current state)

Module 2: Security Hooks (T1)

Most critical, adopt first:

security-gate.sh
prompt-guard.sh
Test with safe commands

Module 3: Rules (Priority)

Start with 2-3 critical rules:

00-project-overview.mdc
01-core-standards.mdc
Tech-specific rule (e.g., 02-code-style.mdc)

Module 4: Commands

Essential only:

update-state.md
load-context.md

Module 5: Documentation

Create docs/context/ structure
Migrate existing docs
Create initial ADR-001

Module 6: Full Adoption

Add remaining:

T2-T4 hooks
All rules
All commands
SubAgents
Skills

Phase 4: Validation

Per-module verification:

Run git status — check what's changed
Test hooks — verify they work
Test commands — ensure / works
User review — approve changes

Output

## Paradigm Adoption Report

### Modules Adopted
| Module | Status | Files Changed |
|--------|--------|---------------|
| Core | ✅ | [N files] |
| Hooks T1 | ✅ | security-gate, prompt-guard |
| ... | ... | ... |

### Remaining Work
- [ ] Full T2-T4 hooks
- [ ] Complete rule set
- [ ] ...

### Recommendations
- [Specific next steps]

Conservative Approach

For sensitive production projects:

Start with read-only components (rules, docs)
Add hooks in monitor-only mode first
Gradually enable enforcement
Full adoption over multiple sessions

# /paradigm-adopt — Adopt Paradigm Gradually Adopt CursorHarness engineering paradigm in an existing (brownfield) project. ## Phase 1: Audit Current State Analyze existing project: 1. **Structure audit**: Current directory layout 2. **Tech stack detection**: Language, framework 3. **Existing conventions**: Any current standards? 4. **Git state**: Branch, recent commits 5. **Conflicts**: What will need adaptation? ## Phase 2: Module-by-Module Plan Create phased adoption plan: | Phase | Module | Action | Confirm? | |-------|--------|--------|----------| | 1 | Core config | .cursor/, AGENTS.md, STATE.md | ✅ | | 2 | Hooks | T1 (security) first | ✅ | | 3 | Rules | Priority rules only | ✅ | | 4 | Commands | Essential commands | ✅ | | 5 | Docs | architecture.md, standards | ✅ | | 6 | Full adoption | Remaining components | ✅ | ## Phase 3: Execute (Per Module) For each module, user confirms before proceeding: ### Module 1: Core Configuration Copy without overwrite: - `.cursor/` directory - `AGENTS.md` (adapt project name) - `STATE.md` (analyze current state) ### Module 2: Security Hooks (T1) Most critical, adopt first: - `security-gate.sh` - `prompt-guard.sh` - Test with safe commands ### Module 3: Rules (Priority) Start with 2-3 critical rules: - `00-project-overview.mdc` - `01-core-standards.mdc` - Tech-specific rule (e.g., `02-code-style.mdc`) ### Module 4: Commands Essential only: - `update-state.md` - `load-context.md` ### Module 5: Documentation - Create `docs/context/` structure - Migrate existing docs - Create initial ADR-001 ### Module 6: Full Adoption Add remaining: - T2-T4 hooks - All rules - All commands - SubAgents - Skills ## Phase 4: Validation Per-module verification: 1. Run `git status` — check what's changed 2. Test hooks — verify they work 3. Test commands — ensure `/` works 4. User review — approve changes ## Output ``` ## Paradigm Adoption Report ### Modules Adopted | Module | Status | Files Changed | |--------|--------|---------------| | Core | ✅ | [N files] | | Hooks T1 | ✅ | security-gate, prompt-guard | | ... | ... | ... | ### Remaining Work - [ ] Full T2-T4 hooks - [ ] Complete rule set - [ ] ... ### Recommendations - [Specific next steps] ``` ## Conservative Approach For sensitive production projects: 1. Start with **read-only** components (rules, docs) 2. Add hooks in **monitor-only** mode first 3. Gradually enable enforcement 4. Full adoption over multiple sessions

{ "prompt": "# /paradigm-adopt — Adopt Paradigm Gradually\n\nAdopt CursorHarness engineering paradigm in an existing (brownfield) project.\n\n## Phase 1: Audit Current State\n\nAnalyze existing project:\n1. **Structure audit**: Current directory layout\n2. **Tech stack detection**: Language, framework\n3. **Existing conventions**: Any current standards?\n4. **Git state**: Branch, recent commits\n5. **Conflicts**: What will need adaptation?\n\n## Phase 2: Module-by-Module Plan\n\nCreate phased adoption plan:\n\n| Phase | Module | Action | Confirm? |\n|-------|--------|--------|----------|\n| 1 | Core config | .cursor/, AGENTS.md, STATE.md | ✅ |\n| 2 | Hooks | T1 (security) first | ✅ |\n| 3 | Rules | Priority rules only | ✅ |\n| 4 | Commands | Essential commands | ✅ |\n| 5 | Docs | architecture.md, standards | ✅ |\n| 6 | Full adoption | Remaining components | ✅ |\n\n## Phase 3: Execute (Per Module)\n\nFor each module, user confirms before proceeding:\n\n### Module 1: Core Configuration\nCopy without overwrite:\n- `.cursor/` directory\n- `AGENTS.md` (adapt project name)\n- `STATE.md` (analyze current state)\n\n### Module 2: Security Hooks (T1)\nMost critical, adopt first:\n- `security-gate.sh`\n- `prompt-guard.sh`\n- Test with safe commands\n\n### Module 3: Rules (Priority)\nStart with 2-3 critical rules:\n- `00-project-overview.mdc`\n- `01-core-standards.mdc`\n- Tech-specific rule (e.g., `02-code-style.mdc`)\n\n### Module 4: Commands\nEssential only:\n- `update-state.md`\n- `load-context.md`\n\n### Module 5: Documentation\n- Create `docs/context/` structure\n- Migrate existing docs\n- Create initial ADR-001\n\n### Module 6: Full Adoption\nAdd remaining:\n- T2-T4 hooks\n- All rules\n- All commands\n- SubAgents\n- Skills\n\n## Phase 4: Validation\n\nPer-module verification:\n1. Run `git status` — check what's changed\n2. Test hooks — verify they work\n3. Test commands — ensure `/` works\n4. User review — approve changes\n\n## Output\n\n```\n## Paradigm Adoption Report\n\n### Modules Adopted\n| Module | Status | Files Changed |\n|--------|--------|---------------|\n| Core | ✅ | [N files] |\n| Hooks T1 | ✅ | security-gate, prompt-guard |\n| ... | ... | ... |\n\n### Remaining Work\n- [ ] Full T2-T4 hooks\n- [ ] Complete rule set\n- [ ] ...\n\n### Recommendations\n- [Specific next steps]\n```\n\n## Conservative Approach\n\nFor sensitive production projects:\n1. Start with **read-only** components (rules, docs)\n2. Add hooks in **monitor-only** mode first\n3. Gradually enable enforcement\n4. Full adoption over multiple sessions", "variables": [], "notes": "Brownfield adoption - gradually adopt CursorHarness in existing project", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/ZenRay/CursorTemplate", "path": ".cursor/commands/paradigm-adopt.md", "ref": "0643e2b5863ee982562d545a9276c08523c183b8", "url": "https://github.com/ZenRay/CursorTemplate/blob/0643e2b5863ee982562d545a9276c08523c183b8/.cursor/commands/paradigm-adopt.md", "key": "ZenRay/CursorTemplate/.cursor/commands/paradigm-adopt.md" } } }

paradigm-adopt

About