القائمة
Configure the Structured Agentic Development Workflow — set testing methodology (TDD/BDD), output style (caveman brevity), and persist preferences to agent memory.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Maintain and manage features and bugs on GitHub. Creates, updates, lists, and links GitHub issues and project cards.
Recommend what to work on next by reading the backlog (bugs.md, features.md, plans/) and considering what is already loaded in the current conversation context. Minimizes context thrash — prefers tasks aligned with current context. Recommends bugs when context is low, features when resources are plentiful.
Write a formal phased implementation plan to docs/plans/new/. Use after brainstorming is complete and a direction has been chosen. Creates a plan file that decouples the planning agent from the building agent.
Independent third-person code review. Use after ALL build phases are complete for a holistic review of the entire feature, or anytime the user wants a quality gate. Switches persona to a Senior Architect who did NOT write the code and now owns it — it must meet world-class standards.
The Structured Agentic Development Workflow — orchestrates brainstorm, write-plan, build-phase, 3p-review, handoff-summary, triage, test-driven-development, systematic-debugging, and verification-before-completion skills. Use when starting new work, switching between development phases, or when the user asks about the workflow. A dedicated build model uses the build-model workflow instead of this one.
Entry point for a dedicated build model — a smaller/faster model run in a session whose only job is to build a plan, review it, and hand off. Orchestrates /build-phase across all phases, then /3p-review (loop until clean), then /handoff-summary, then pauses. Does NOT run /verification-before-completion. The main model uses agentic-workflow instead.
| name | workflow-config |
| description | Configure the Structured Agentic Development Workflow — set testing methodology (TDD/BDD), output style (caveman brevity), and persist preferences to agent memory. |
| argument-hint | ["preferences","e.g. \"enable caveman full\" or \"use bdd\""] |
| user-invocable | true |
| allowed-tools | Read, Grep, Glob |
You are configuring the Structured Agentic Development Workflow.
Parse the user's preferences from: $ARGUMENTS
Then persist each preference to your agent's persistent memory so it applies across all future workflow phases and sessions.
/test-driven-development.Only one can be active at a time. Setting one disables the other.
When caveman is enabled, ALL workflow skills (brainstorm, write-plan, build-phase, 3p-review, triage, systematic-debugging, verification-before-completion) adapt their output to the requested brevity level. Technical accuracy is never sacrificed — only prose style changes.
Important: This workflow does NOT bundle or vendor the Caveman skills package. If the user wants caveman to also govern the agent's base system prompt (outside of workflow skills), they should install the caveman package separately (e.g., via npx @anthropics/skills). The workflow's caveman compatibility works independently — it adapts workflow skill output regardless of whether the caveman package is installed.
features.md, bugs.md, or under docs/plans/) for tracking backlog. GitHub integration is disabled.origin remote, so no further configuration is required for the common case.Optional GitHub keys (only set when you need to override the defaults):
owner/repo format (e.g., nikhilw/structured-agentic-workflow). Leave unset to auto-derive from git remote get-url origin. Useful when issues live in a different repo than origin.Save each preference as a memory entry in your agent's persistent memory system. Use whatever memory mechanism your platform provides — the key requirement is that the preference survives across conversation sessions.
Memory entries should be structured as:
workflow-config:<preference-name> (e.g., workflow-config:testing-methodology, workflow-config:caveman-level, workflow-config:use-github-issues, workflow-config:github-repo, workflow-config:github-project-id)bdd, full, true/false, owner/repo)The following are NOT configurable — they are core workflow guarantees:
/verification-before-completion) — Always mandatory. Cannot be disabled.new/ → plans/ → done/. Cannot be bypassed.After saving preferences, confirm what was set:
## Workflow Configuration Updated
- Testing methodology: [TDD / BDD]
- Output style: [normal / caveman lite / caveman full / caveman ultra]
- Use GitHub Issues: [true / false]
- GitHub repo: [owner/repo override / auto-derived from origin]
- GitHub Project ID: [project ID or not set]
These preferences are saved to memory and will apply to all future workflow phases.
If the user asks to see current configuration, read the preferences from memory and display them in the same format.