azaion/gps-denied-desktop
1
0
Fork 0
mirror of https://github.com/azaion/gps-denied-desktop.git synced 2026-04-22 09:06:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Sync .cursor from suite (autodev orchestrator + monorepo skills)

Browse Source
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-04-18 22:04:15 +03:00
parent 7df4f7707f
commit eb54bb2d37
60 changed files with 4232 additions and 1728 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.cursor/README.md
+12 -12
View File
@@ -1,9 +1,9 @@
## How to Use
Type `/autopilot` to start or continue the full workflow. The orchestrator detects where your project is and picks up from there.
Type `/autodev` to start or continue the full workflow. The orchestrator detects where your project is and picks up from there.
```
/autopilot — start a new project or continue where you left off
/autodev — start a new project or continue where you left off
```
If you want to run a specific skill directly (without the orchestrator), use the individual commands:
@@ -19,13 +19,13 @@ If you want to run a specific skill directly (without the orchestrator), use the
## How It Works
The autopilot is a state machine that persists its state to `_docs/_autopilot_state.md`. On every invocation it reads the state file, cross-checks against the `_docs/` folder structure, shows a status summary with context from prior sessions, and continues execution.
The autodev is a state machine that persists its state to `_docs/_autodev_state.md`. On every invocation it reads the state file, cross-checks against the `_docs/` folder structure, shows a status summary with context from prior sessions, and continues execution.
```
/autopilot invoked
/autodev invoked
│
▼
Read _docs/_autopilot_state.md → cross-check _docs/ folders
Read _docs/_autodev_state.md → cross-check _docs/ folders
│
▼
Show status summary (progress, key decisions, last session context)
@@ -37,7 +37,7 @@ Execute current skill (read its SKILL.md, follow its workflow)
Update state file → auto-chain to next skill → loop
```
The state file tracks completed steps, key decisions, blockers, and session context. This makes re-entry across conversations seamless — the autopilot knows not just where you are, but what decisions were made and why.
The state file tracks completed steps, key decisions, blockers, and session context. This makes re-entry across conversations seamless — the autodev knows not just where you are, but what decisions were made and why.
Skills auto-chain without pausing between them. The only pauses are:
- **BLOCKING gates** inside each skill (user must confirm before proceeding)
@@ -49,13 +49,13 @@ A typical project runs in 2-4 conversations:
- Session 3: Implement (may span multiple sessions)
- Session 4: Deploy
Re-entry is seamless: type `/autopilot` in a new conversation and the orchestrator reads the state file to pick up exactly where you left off.
Re-entry is seamless: type `/autodev` in a new conversation and the orchestrator reads the state file to pick up exactly where you left off.
## Skill Descriptions
### autopilot (meta-orchestrator)
### autodev (meta-orchestrator)
Auto-chaining engine that sequences the full BUILD → SHIP workflow. Persists state to `_docs/_autopilot_state.md`, tracks key decisions and session context, and flows through problem → research → plan → decompose → implement → deploy without manual skill invocation. Maximizes work per conversation with seamless cross-session re-entry.
Auto-chaining engine that sequences the full BUILD → SHIP workflow. Persists state to `_docs/_autodev_state.md`, tracks key decisions and session context, and flows through problem → research → plan → decompose → implement → deploy without manual skill invocation. Maximizes work per conversation with seamless cross-session re-entry.
### problem
@@ -136,13 +136,13 @@ Bottom-up codebase documentation. Analyzes existing code from modules through co
7. /retrospective — metrics, trends, improvement actions → _docs/06_metrics/
```
Or just use `/autopilot` to run steps 0-5 automatically.
Or just use `/autodev` to run steps 0-5 automatically.
## Available Skills
| Skill | Triggers | Output |
|-------|----------|--------|
| **autopilot** | "autopilot", "auto", "start", "continue", "what's next" | Orchestrates full workflow |
| **autodev** | "autodev", "auto", "start", "continue", "what's next" | Orchestrates full workflow |
| **problem** | "problem", "define problem", "new project" | `_docs/00_problem/` |
| **research** | "research", "investigate" | `_docs/01_solution/` |
| **plan** | "plan", "decompose solution" | `_docs/02_document/` |
@@ -170,7 +170,7 @@ Or just use `/autopilot` to run steps 0-5 automatically.
```
_project.md — project-specific config (tracker type, project key, etc.)
_docs/
├── _autopilot_state.md — autopilot orchestrator state (progress, decisions, session context)
├── _autodev_state.md — autodev orchestrator state (progress, decisions, session context)
├── 00_problem/ — problem definition, restrictions, AC, input data
├── 00_research/ — intermediate research artifacts
├── 01_solution/ — solution drafts, tech stack, security analysis