Repository navigation
Phase 3.5: lift kendo issue-creation expansion into newbranch, plan-feature, task-writer (with placeholders) - #4
Merged
Conversation
…k-writer
Phase 3.5 of the skill lift roadmap. Catalog versions of these three
skills were scope-pure (branch creator, planner, task writer); the
kendo consumer expanded them with issue-first behavior — find or create
the Kendo issue, bundle its context via prepare-issue-context-tool,
start work via start-work-on-issue-tool. Per the resolved decision in
the lift roadmap, all consumers use Kendo MCP, so this expansion lifts
verbatim with placeholders for the parts that vary per tenant:
- {{PROJECT_ID}} — Kendo project ID (e.g. 1)
- {{ISSUE_KEY_PREFIX}} — issue key prefix (e.g. KD)
- {{DEFAULT_BRANCH}} — base branch name (e.g. development)
- {{TENANT}} — tenant subdomain (e.g. script.kendo.dev)
newbranch: now an issue-first flow — find/create issue, bundle context,
create branch with key prefix, start-work-on-issue. Keeps the
--no-track + push -u guard from the catalog version.
plan-feature: Phase 0 (parse arguments) and Phase 1a (check the board)
now Kendo-specific with placeholders. Phase 4a points at
issue-templates.md and uses mcp__kendo__create-issue-tool.
task-writer: Output section now derives ticket key from branch/plan/ask,
creates issue via /kendo-mcp + issue-templates.md if needed, uses
returned key for directory naming.
Tool prefix is mcp__kendo__ throughout (matches the most consistent
kendo convention; consumers configuring the MCP server under a
different name adapt at adoption time).
4 tasks
jasperboerhof
added a commit
that referenced
this pull request
May 5, 2026
…ences Phase 4 (stacked on PR #4): factor plan-feature inline content into 5 reference files
4 tasks done
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
1 participant
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
Phase 3.5 of the skill lift roadmap. The kendo consumer's
newbranch,plan-feature, andtask-writercarry an issue-first expansion (find/create Kendo issue, bundle context, start work) that the catalog versions don't have. Per the resolved decision (all consumers use Kendo MCP, lift with{{PLACEHOLDER}}substitution), this PR brings the expansion into catalog with placeholders for the parts that vary per tenant.Placeholders introduced
{{PROJECT_ID}}1{{ISSUE_KEY_PREFIX}}KD{{DEFAULT_BRANCH}}development{{TENANT}}script(i.e.script.kendo.dev)Per-skill changes
skills/newbranch/SKILL.md(55 → ~115 lines)mcp__kendo__search-issues-tool/kendo://issues/{key}/mcp__kendo__create-issue-tool), bundle context withmcp__kendo__prepare-issue-context-tool, create branch with key prefix, callmcp__kendo__start-work-on-issue-tool.issue-templates.mdlifted in Phase 1.--no-track+push -uguard.skills/plan-feature/SKILL.mdmcp__kendo__search-issues-toolandkendo://projects/{{PROJECT_ID}}/epics.issue-templates.mdand usesmcp__kendo__create-issue-toolwithproject_id: {{PROJECT_ID}}.skills/task-writer/SKILL.md/kendo-mcp+issue-templates.mdif needed, uses the returned key for directory naming.Test plan
script.kendo.dev, raw1for project_id, rawKDfor prefix, rawdevelopmentfor branch).../kendo-mcp/references/issue-templates.mdresolves both in catalog and in any consumer that copies these skills.mcp__kendo__prefix consistently (kendo's own consumer is mixedmcp__kendo__/mcp__kendo.dev__; catalog standardises on the shorter form).🤖 Generated with Claude Code