| title | Cursor walkthrough |
|---|---|
| folder | docs/cross-tool |
| description | How to use Specorator from Cursor with AGENTS.md and Markdown workflow artifacts. |
- Open the repository folder in Cursor and pin
AGENTS.md,memory/constitution.md, anddocs/specorator.mdas context. - Start with a precise prompt: "Follow Specorator Stage 1-3 for
<feature>; ask clarifying questions before writing requirements." - Have Cursor draft
specs/<feature>/idea.md, thenresearch.md, thenrequirements.md.
Invoke specialists by naming their role and source file: "Use .claude/agents/pm.md as the role contract for this requirements pass." Keep one stage per chat thread when the output needs review.
Use .claude/skills/<name>/SKILL.md files as prompt context for recurring practices. For architecture improvement, pin .claude/skills/improve-codebase-architecture/SKILL.md and ask Cursor to list deepening opportunities before making edits.
All durable output belongs in specs/<feature>/. Use workflow-state.md as the pickup point when reopening Cursor later.
Run npm run verify in the integrated terminal before committing. If the change touches generated command or script docs, run the matching npm run fix:* command first.