clodbridge: Skill for Cursor

Manage Scope Iteratively

The Principle

Deliver incrementally. Each commit is a checkpoint for user feedback.

Increment = One Commit

An "increment" is exactly one commit's worth of work:

Increment = 1 commit = 1-5 files = < 500 lines = 1 feature/fix

After completing an increment:

1. Commit the code
2. Check in with the user ("X is done. Should I proceed?")
3. Wait for feedback
4. Continue based on guidance

When to Check In

After completing:

Milestone	Check In?	What to Say
New type definition + tests pass	YES	"Types done. Should I proceed with parsing?"
Parsing function + tests pass	YES	"Parsing works. Ready for discovery modules?"
Major subsystem (server, tools, resources)	YES	"Server core done. Ready for tools?"
You're about to start something big (> 200 LOC)	YES	"About to implement MCP resources. Proceed?"
A design decision arises	YES	"Found a design question: MCP Resources schema?"
You hit a blocker	YES	"Can't install npm. Options: ..."
Integration point between systems	YES	"Reader + server wired. Proceed with tools?"

Checkpoint Template

After a commit:

✅ "{Feature description} is complete.

{Optional: What was done}
- Implemented {module}
- Wrote {N} tests
- All tests pass

{Optional: What's next}
Next: {next milestone}

Should I proceed?"

Examples:

Example 1:

✅ "Types and interfaces are defined.

- RuleMode type (4 modes)
- CursorRule, CursorSkill, CursorAgent interfaces
- CursorReader facade

Next: Implement parsing with gray-matter.

Should I proceed?"

Example 2:

✅ "Parsing works with all tests passing.

- parseRuleFile, parseSkillFile, parseAgentFile
- RuleMode derivation (always/auto-attached/agent-requested)
- 15 tests, all passing

Next: Implement discovery modules (rules, skills, agents).

Any feedback before I continue?"

Example 3:

⚠️ "Design question: How should MCP Resources expose data?

Options:
A) Raw file content only (cursor://rules/{name} returns .mdc text)
B) JSON indices only (cursor://rules returns structured list)
C) Both raw and JSON
D) Skip resources; tools are sufficient

What's your preference?"