Add Cursor IDE plugin support - #14
Open
Mustaffa-Gamall wants to merge 43 commits into
Open
Mustaffa-Gamall wants to merge 43 commits into
Mustaffa-Gamall wants to merge 43 commits into
Conversation
feat: integrate Codemap for token-efficient codebase navigation
Introduces a new phase between Design (2) and API Architecture (2.5) that uses the SuperDesign MCP to generate polished HTML screens from styled-dsl.yaml for visual approval before code is written, preventing expensive rework. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
PM QA agent that translates acceptance criteria from roadmap.yaml into Maestro test flows, runs them, and produces pass/fail acceptance reports. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds acceptance testing as Step 3D in the per-feature workflow and as a regression suite in Phase 4. Features now require an ACCEPTED verdict from pm-maestro-reviewer before proceeding. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds support for existing codebases with three new skills: - /onboard: 5-step interactive wizard (detect, import, audit, backfill, finalize) - /setup-mcp: MCP server setup helper with curated 8-tool registry - /feature: Add features to roadmap with git workflow integration Updates phase-setup to detect existing projects, phase-3 and phase-4 for project-type awareness (fullstack/frontend_only/backend_only/mobile) and flexible api_contract_path. CLAUDE.md updated with commands, project types, and git workflow sections. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Move curated MCP registry from inline SKILL.md to mcp-registry.yaml for easier editing and maintenance - Replace Anthropic Jira/Confluence MCPs with official Atlassian Rovo MCP (https://mcp.atlassian.com/v1/mcp, OAuth, covers both tools) - Add shared_with field so Jira+Confluence share one server config - SKILL.md now references registry via ref:skills/setup-mcp/mcp-registry.yaml Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Rename skill directories: onboard → archflow-onboard, setup-mcp → archflow-setup-mcp, feature → archflow-feature - Update all cross-references across SKILL.md files, CLAUDE.md, phase-setup.md, phase-3-implementation.md, phase-onboarding.md - Add SuperDesign MCP to registry (stdio, Phase 2.25, not onboarding-only) Commands are now: /archflow-onboard - Onboard existing codebase /archflow-setup-mcp - Configure MCP servers /archflow-feature - Add features to roadmap Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Consolidate three separate skills (archflow-onboard, archflow-setup-mcp, archflow-feature) into a single /archflow skill with commands/ subdirectory. Update all references from /archflow-X to /archflow X syntax. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- README with centered header, shield badges, phase overview, agent docs, slash commands, project types, git workflow, and core principles - SVG overview diagram showing all 6 phases with agent assignments - MIT license file Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Templates were experimental and no longer used. Cleaned up all references from README (file structure, install, contributing). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Rewrite onboard.md from 5-step linear wizard to 3-phase model: - Phase A: Interactive collection (gather all user input upfront) - Phase B: Autonomous agent dispatch (parallel specialized agents) - Phase C: Synthesis and presentation (reconcile and present results) Update phase-onboarding.md with: - Structured audit output schema (.onboard-audit-report.yaml) - Design token and route/API extraction rules - Agent prompt templates for all 9 onboarding agents - Agent filtering table by project type - Progress file schema with resume support - CLAUDE.md creation/update in finalization step - Glob-based cleanup of all .onboard-* temp files Update feature.md with scope-based filtering: - Every epic now requires a scope field (backend/frontend/mobile/both/unknown) - /archflow feature filters roadmap by project_type compatibility - Mismatched features hidden by default with "show all" option and warnings Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update internal references in all phase files to use .archflow/ paths instead of bare phases/ paths. Add instructions.md for hook-based instruction loading. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- CLAUDE.md: Update phase file paths to .archflow/phases/ - README.md: Update references to new directory structure - .gitignore: Add .archflow temp files and agent artifacts - SKILL.md: Update skill paths for .archflow/ layout - setup-mcp.md: Update MCP command references - pm-maestro-reviewer.md: Improve acceptance testing agent Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- README: Add "How onboarding works" section showing Phase A/B/C pipeline - README: Update onboard/feature command descriptions for new architecture - README: Add scope-based feature filtering mention - .claude/settings.json: SessionStart hook to reload .archflow/instructions.md after context compaction (startup|resume|compact) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…structure Restructure into .archflow/ directory with redesigned onboarding
…-setup Add Archflow README, overview diagram, and project setup
- Add .claude-plugin/marketplace.json as marketplace registry - Add plugin/ directory with full framework (agents, skills, phases, hooks) - Update README Quick Start to use `claude plugin marketplace add/install` - Update File Structure section to show marketplace + project layout Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add init.md command (creates .archflow/ state files for new projects)
- Add init route to SKILL.md subcommand router
- Add init to Available Commands in CLAUDE.md and instructions.md
- Sync all changes to plugin/ directory
- Fix ${CLAUDE_PLUGIN_ROOT} reference to relative path in init.md
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add plugin marketplace structure and /archflow init command
- Single-page landing page at docs/index.html - Dark premium design with indigo accent - All 9 sections: hero, proof bar, problem, how it works, phases, existing projects, commands, project types, install CTA - Includes landing page plan and LinkedIn launch post drafts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add landing page for GitHub Pages
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Add website link to README
- Move Quick Start to section 2 (right after "What is Archflow?") - Merge "Why Archflow?" + Core Principles into unified "How It Works" section - Pull "Works with Existing Projects" into its own prominent section - Collapse 7 agent sub-tables into 1 compact table - Collapse File Structure and External Tools into <details> tags - Add zero-risk line after install: "Free and open source. No lock-in." - Reframe internal concerns as developer benefits - Break long sentences, tighten copy throughout Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Rewrite README for clarity and developer appeal
New section between Problem and How It Works with a visual comparison SVG: vibe coding's guess-and-loop cycle vs Archflow's structured phases with human approval gates. Addresses the AZidan#1 question from users: "How is this different from other AI coding tools?" Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…tes, acceptance testing (v1.1.0) Address 8 structural gaps (6.25% → 100% compliance) identified during real-world use: - Git from day one: init/onboard require git, phases commit artifacts before transition - Subtask tracking: dual-file updates in workflow.md, extended schema in feature.md - Branch-before-code: pre-dispatch validation requires task branch - Approval gates: Step 3F mandatory user approval with structured presentation - Feature serialization: one story at a time, clarified parallelism rules - Agent end-of-task: completion protocols for ui/api/qa/pm-maestro agents - Acceptance auto-trigger: 3C gate + auto-dispatch 3D, rejection loops - Phase transition validation: artifact/git/approval checklists for all phases Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Enforce governance gaps — git, subtask tracking, approval gates, acceptance testing (v1.1.0)
- Add .archflow/schemas/roadmap-schema.yaml as the single source of truth for roadmap format
- Update onboard, feature, and feature-planner to enforce {text,met} for acceptance_criteria and {text,completed} for subtasks
- Add gap reports and format incompatibility docs
- Bump plugin version 1.1.0 → 1.1.1
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fix/canonical roadmap schema
…v1.2.1
- Add exhaustive roadmap format validation to onboard audit (Step 1a): checks
top-level structure, epic/story required fields and ID patterns, enum values,
acceptance_criteria/{text,met} and subtasks/{text,completed} item shapes,
sprint ID pattern, sprint stories as string references, referential integrity,
and no duplicate story IDs across sprints
- Roadmap with violations now reports as PARTIAL (not DONE) in audit
- C1 reconciliation auto-fixes violations when writing final roadmap.yaml
- C3 gap report surfaces all violations with YAML path, rule, and found value
- Bump plugin 1.2.0 → 1.2.1
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Fix canonical roadmap schema + onboard format validation (v1.2.1)
Previously, running /archflow onboard on an already-onboarded project would show a static status summary and exit, bypassing roadmap format validation entirely. Now the entry check runs roadmap.yaml format validation first: - No violations → show status summary as before - Violations found → show all violations and offer to auto-fix, walk through interactively, or skip Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…d-format-check Fix onboard already-onboarded path to run format validation (v1.2.2)
…1.2.3) The previous fix added an Already Onboarded path but the model still pattern-matched to the status summary without running validation. Restructure Entry Check to require explicit tool calls in sequence: - Step E1: check for .onboard-progress.yaml - Step E2: Read tool call on roadmap.yaml (mandatory, non-deferrable) - Step E2a: inline validation rules (no external file reference needed) - Step E3: read current-phase.yaml and branch on violations Inline all format validation rules so no secondary file read is needed. Include auto-fix rules directly in the violations branch. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…yment (v1.2.3) Claude Code only deploys skills/archflow/ to ~/.claude/_skills/archflow/. The .archflow/ directory from the plugin cache is not propagated to the skills deployment, so 14 files referenced by skill commands were unreachable at runtime: - 11 phase files (phase-onboarding, phase-setup, phase-1 through phase-6) - 1 schema file (roadmap-schema.yaml) - 1 workflow file (workflow.md) These are now included directly in skills/archflow/ so they ship with the _skills deployment. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add phases, schemas, workflow to skill folder for deployment (v1.2.3)
Port the Archflow plugin to work with Cursor IDE alongside the existing Claude Code plugin using a shared plugin/ directory — zero file duplication. Both IDEs discover their own manifest (.claude-plugin/ vs .cursor-plugin/) and ignore the other. The only Cursor-specific addition is rules/archflow-instructions.mdc for Cursor's always-applied workspace rules. Added .cursor-plugin/marketplace.json at repo root for Cursor Marketplace submission. README updated with Cursor installation docs (marketplace + manual fallback) and updated file structure showing dual-manifest approach.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
plugin/directory using a dual-manifest approach — zero file duplication. Both Claude Code and Cursor discover their own manifest (.claude-plugin/plugin.jsonvs.cursor-plugin/plugin.json) and ignore the other.plugin/:.cursor-plugin/plugin.json(Cursor manifest with marketplace metadata) andrules/archflow-instructions.mdc(Cursor's always-applied workspace rules format)..cursor-plugin/marketplace.jsonat repo root for Cursor Marketplace submission (parallel to the existing.claude-plugin/marketplace.json).Changes (4 files)
New files
.cursor-plugin/marketplace.jsonplugin/.cursor-plugin/plugin.jsonplugin/rules/archflow-instructions.mdc.mdcformat with YAML frontmatter)Modified files
README.mdWhy dual-manifest instead of separate directories?
Both Claude Code and Cursor use the same agents, skills, hooks, and phases. The only differences are:
.claude-plugin/vs.cursor-plugin/)rules/archflow-instructions.mdc(Claude Code ignores therules/folder)Each IDE discovers its own manifest and ignores the other. This means the shared
plugin/directory works as-is for both — no files need to be duplicated.Marketplace submission
After this PR is merged, the repo can be submitted to the Cursor Marketplace at cursor.com/marketplace/publish. The
.cursor-plugin/marketplace.jsonat the repo root follows Cursor's multi-plugin repository format.Test plan
plugin/directory contains both.claude-plugin/plugin.jsonand.cursor-plugin/plugin.jsonrules/archflow-instructions.mdcloads correctly as always-applied rule in Cursor.claude-plugin/unchanged)