skills/roadmap-manage/SKILL.md
<agentic_guild_skill> <skill_definition> <name>roadmap-manage</name> <description>Add, prioritize, catalog, and update items in the project roadmap.</description> </skill_definition> <state_machine_directives> 1. NEVER execute more than ONE <step> per response. 2. When you see [PAUSE], you MUST completely stop generating text and wait for the user to reply. 3. Always end your response by summarizing our progress in a conversational manner and gently inviting the user t
npx skillsauth add jdugarte/agentcore skills/roadmap-manageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<agentic_guild_skill> <skill_definition> <name>roadmap-manage</name> <description>Add, prioritize, catalog, and update items in the project roadmap.</description> </skill_definition>
<state_machine_directives>
1. NEVER execute more than ONE <step> per response.
2. When you see [PAUSE], you MUST completely stop generating text and wait for the user to reply.
3. Always end your response by summarizing our progress in a conversational manner and gently inviting the user to proceed.
</state_machine_directives>
<hard_constraints>
NEVER use any tool to execute git commit, git push, or git merge. These commands are STRICTLY FORBIDDEN.
When a commit is appropriate, output a suggested message as a plain-text code block only. The user runs all git commands themselves.
</hard_constraints>
<pre_flight>
<directive>Before executing the workflow, verify the necessary context exists.</directive>
<check>Verify docs/ROADMAP.md exists. If not, gently inform the user and suggest running sync.sh to initialize it, or offer to create a minimal structure with Done, In Progress, Pending, Backlog sections.</check>
</pre_flight>
data-ai
<agentic_guild_skill> <skill_definition> <name>update-agentic-guild</name> <description>Intelligently synchronizes and updates agentic:guild OS components (skills, rules, templates) from the global repository, using AI to merge changes gracefully. For projects that already have agentic:guild installed, this skill replaces running sync.sh manually.</description> </skill_definition> <state_machine_directives> 1. NEVER execute more than ONE <step> per response. 2. When you se
development
<agentic_guild_skill> <skill_definition> <name>sync-docs</name> <description>Keeps project docs in sync with branch changes and with task memory. Uses two inputs: (1) the branch diff — to infer code/schema-driven doc updates; (2) the active task session file when present — semantically analyzed so domain, decisions, data semantics, and rule-worthy content are pushed to the right docs. Does not dump raw session content; synthesizes and places knowledge by type.</description> </skill_d
tools
<agentic_guild_skill> <skill_definition> <name>status-check</name> <description>Rehydrates project context and acts as the GPS for agentic:guild execution state.</description> </skill_definition> <state_machine_directives> 1. NEVER generate or modify application code during this skill. 2. Your ONLY job is diagnosis and context rehydration. </state_machine_directives> <hard_constraints> NEVER use any tool to execute `git commit`, `git push`, or `git merge`. These co
development
<agentic_guild_skill> <skill_definition> <name>start-task</name> <description>Initiates the process of building a new feature, bugfix, refactor, or chore. Enforces strict QA discovery, implementation planning, and TDD.</description> </skill_definition> <state_machine_directives> 1. NEVER execute more than ONE <step> per response. 2. When you see [PAUSE], you MUST completely stop generating text and wait for the user to reply. 3. Always end your response by summarizing