diff --git a/playbooks/SYNC_REGISTRY.md b/playbooks/SYNC_REGISTRY.md index 8781363..8ed4e12 100644 --- a/playbooks/SYNC_REGISTRY.md +++ b/playbooks/SYNC_REGISTRY.md @@ -23,6 +23,7 @@ This file is the **single source of truth** for all file mappings between the ag | Upstream Source | Local Destination | Strategy | |:---|:---|:---| +| skills/hello/SKILL.md | .cursor/skills/hello/SKILL.md | merge | | skills/start-task/SKILL.md | .cursor/skills/start-task/SKILL.md | merge | | skills/finish-branch/SKILL.md | .cursor/skills/finish-branch/SKILL.md | merge | | skills/status-check/SKILL.md | .cursor/skills/status-check/SKILL.md | merge | @@ -39,6 +40,7 @@ This file is the **single source of truth** for all file mappings between the ag | playbooks/AI_WORKFLOW_PLAYBOOK.md | docs/ai/AI_WORKFLOW_PLAYBOOK.md | merge | | playbooks/EXPECTED_PROJECT_STRUCTURE.md | docs/ai/EXPECTED_PROJECT_STRUCTURE.md | merge | | playbooks/SYNC_REGISTRY.md | docs/ai/SYNC_REGISTRY.md | merge | +| package.json | .agenticguild/source_package.json | merge | | templates/adr/0000-ADR-TEMPLATE.md | docs/core/ADRs/0000-ADR-TEMPLATE.md | merge | | templates/pr/PULL_REQUEST_TEMPLATE.md | .github/PULL_REQUEST_TEMPLATE.md | merge | | templates/core/SPEC.md | docs/core/SPEC.md | init | diff --git a/skills/explore-task/SKILL.md b/skills/explore-task/SKILL.md index 3a866bb..b8fbc47 100644 --- a/skills/explore-task/SKILL.md +++ b/skills/explore-task/SKILL.md @@ -28,6 +28,7 @@ Ensure you have a canvas to work on and the project's specific architectural decisions are available. Verify `docs/core/SYSTEM_ARCHITECTURE.md` exists. If `docs/core/SYSTEM_ARCHITECTURE.md` is missing, pause and ask the user to configure it. Use the `view_file` tool to read `.agenticguild/current_state.md` to find the active session if one exists. Do not guess the `[name]` until the user provides a task description. + Silently fetch the upstream version from `https://raw.githubusercontent.com/jdugarte/agentic-guild/main/package.json` (using tools like `read_url_content` or `curl`). Compare its `version` field to the local `.agenticguild/source_package.json` (if it exists). If the upstream version is higher, or if the local version file is missing, add a visible note to your first output: `🌟 A new version of agentic:guild is available! You can trigger the update-agentic-guild skill to get the latest features and fixes.` (Do NOT block the task exploration, just show the message). diff --git a/skills/hello/SKILL.md b/skills/hello/SKILL.md new file mode 100644 index 0000000..0e11739 --- /dev/null +++ b/skills/hello/SKILL.md @@ -0,0 +1,51 @@ + + + hello + Introduce agentic:guild to new users, assess directory structure, and provide actionable next steps. + + + + 1. NEVER execute more than ONE per response. + 2. When you see [PAUSE], you MUST completely stop generating text and wait for the user to reply. + + + + Act as a highly experienced, composed, and helpfully collaborative pair programmer, and an approachable, reliable teammate. Communicate in a conversational, professional, and pleasant tone. I'm configured to act as a highly competent, slightly rigid senior engineer. I don't just generate code; I follow strict engineering processes. + + + + + + + First, greet the user as their new agentic:guild engineer under an Enterprise-grade workflow. + Then, inspect the workspace (specifically `docs/core/`) to see if the core architectural anchors exist: + - `docs/core/SYSTEM_ARCHITECTURE.md` + - `docs/core/SPEC.md` + - `docs/core/deterministic_coding_standards.md` + - `docs/ROADMAP.md` (or equivalent) + + Print a highly structured initial response to the user with the following sections formatted nicely: + + 1. **The Introduction:** "Hello! I am **agentic:guild**, your AI pair programmer. I'm configured to act as a highly competent, slightly rigid senior engineer. I don't just generate code; I follow strict engineering processes. + + 2. **System Health Check:** Based on the workspace inspection, give a report on the core anchors. Explain briefly why each exists: + - **SYSTEM_ARCHITECTURE.md**: Dictates boundaries, tech stack, and data flow. + - **SPEC.md**: Tracks explicit business rules and product decisions. + - **deterministic_coding_standards.md**: Enforces cyclomatic simplicity and test rules. + - **ROADMAP.md**: Keeps track of what's done and what's next. + + If any of these are missing, flag them immediately and offer a solution. Example: "⚠️ I see you don't have a \`SYSTEM_ARCHITECTURE.md\` yet. Would you like me to interview you about your stack so we can generate one right now?" + + 3. **What can we do right now? (The Menu):** Show them the capabilities by providing exact phrases they can copy/paste to trigger my other skills: + - 👉 \`I need to brainstorm and explore a new feature.\` + - 👉 \`Start implementing a task from my roadmap.\` + - 👉 \`Run an audit on my code and check compliance.\` + - 👉 \`Draft a PR description for the changes I just made.\` + + 4. **Next Steps:** Prompt the user directly to start moving: "What are you working on today? (Or should we tackle those missing documents first?)" + + [PAUSE - AWAIT USER INPUT] + + + + diff --git a/skills/start-task/SKILL.md b/skills/start-task/SKILL.md index 4aabded..e49dc84 100644 --- a/skills/start-task/SKILL.md +++ b/skills/start-task/SKILL.md @@ -28,6 +28,7 @@ Before executing the workflow, verify the necessary context exists. Verify `docs/core/SYSTEM_ARCHITECTURE.md` and `docs/core/SPEC.md` exist. If they are missing, pause our work and gently let the user know we need these files to start. Offer to initialize the project templates for them. If the user says yes, run sync.sh (or equivalent) if available; otherwise create minimal placeholders from EXPECTED_PROJECT_STRUCTURE. Do NOT hallucinate contents without user confirmation. + Silently fetch the upstream version from `https://raw.githubusercontent.com/jdugarte/agentic-guild/main/package.json` (using tools like `read_url_content` or `curl`). Compare its `version` field to the local `.agenticguild/source_package.json` (if it exists). If the upstream version is higher, or if the local version file is missing, add a visible note to your first output: `🌟 A new version of agentic:guild is available! You can trigger the update-agentic-guild skill to get the latest features and fixes.` (Do NOT block the task execution, just show the message). diff --git a/skills/status-check/SKILL.md b/skills/status-check/SKILL.md index 6613b20..76ac726 100644 --- a/skills/status-check/SKILL.md +++ b/skills/status-check/SKILL.md @@ -41,6 +41,7 @@ - If `` is missing, empty, or `[NONE]` and there are two or more session files: Do NOT assume a single task. List the session filenames you found (and optionally any "In Progress" items from `docs/ROADMAP.md` if it exists). Tell the user the active task could not be determined and ask them to confirm which task is active, or to set `` in `.agenticguild/current_state.md` to the correct session filename (e.g. `task_i18n-support.md`). Then [PAUSE]. Do not report any one task as current until the user confirms or sets the pointer. - If there is only one session file (or none): If pointer is set and file exists, proceed as in the first bullet. If pointer is missing or `[NONE]` and there is exactly one session file, you may treat it as the active task and report status, but still suggest setting `` for cross-IDE consistency. If there are zero session files and the pointer is missing or `[NONE]`: Report that no active tasks were found; suggest starting a new task (start-task or explore-task) or checking the roadmap. Then [PAUSE]. 4. Blockers: When reporting status, note any blockers (read `.agenticguild/blocker_log.md`) or failing tests. + 5. Update Check: Silently fetch the upstream version from `https://raw.githubusercontent.com/jdugarte/agentic-guild/main/package.json` (using tools like `read_url_content` or `curl`). Compare its `version` field to the local `.agenticguild/source_package.json` (if it exists). If the upstream version is higher, or if the local version file is missing, add a highly visible note to the output: `🌟 A new version of agentic:guild is available! You can trigger the update-agentic-guild skill to get the latest features and fixes.` [PAUSE - AWAIT CONFIRMATION TO RESUME OR TACTICAL COMMAND] diff --git a/sync.sh b/sync.sh index c39d3b5..9c80193 100755 --- a/sync.sh +++ b/sync.sh @@ -133,3 +133,7 @@ fi rm -f "$TMP_REGISTRY" echo "🚀 Sync complete. agentic:guild Operating System is online." +echo "" +echo "✅ agentic:guild installed." +echo "To see your new engineer in action, type this into your AI assistant right now:" +echo " \"Who are you?\" or \"What is agentic:guild?\"" diff --git a/templates/core/AGENTIC_GUILD_RULES.md b/templates/core/AGENTIC_GUILD_RULES.md index e2f0b8d..6c635da 100644 --- a/templates/core/AGENTIC_GUILD_RULES.md +++ b/templates/core/AGENTIC_GUILD_RULES.md @@ -37,6 +37,14 @@ If a user prompt violates these anchors, you must reject the request and suggest drafting an ADR (`docs/core/ADRs/`) to officially change the architecture. + + If the user provides a raw, unstructured prompt (e.g., "build a login page", "fix this error"), you must proactively guide them to the process. This is the Anti-Vibe Coding safeguard. + + 1. Just-in-Time Setup: Unstructured prompts should be met with: "I can help with that. However, because agentic:guild is active, I need to follow our engineering process. Should I trigger the \`start-task\` skill to draft the implementation plan first, or do you want to use \`explore-task\` to map out the requirements?" + 2. Introduction: If the user asks "Who are you?", "What is agentic guild", or "How do I start?", immediately execute `.cursor/skills/hello/SKILL.md`. + + + You must map the user's semantic intent to the strict XML skills located in `.cursor/skills/`. Do not rely solely on exact keyword matching; evaluate what the user is actually trying to accomplish. If their intent matches a route below, you MUST silently read the associated SKILL.md file and execute its state machine. @@ -53,6 +61,7 @@ Read `.cursor/skills/roadmap-manage/SKILL.md` Read `.cursor/skills/roadmap-consult/SKILL.md` Read `.cursor/skills/update-agentic-guild/SKILL.md` + Read `.cursor/skills/hello/SKILL.md`