[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M735HDRAZF5VM64T7A8DHVZN":3,"skill-same:01M735HDRAZF5VM64T7A8DHVZN":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M735HDRAZF5VM64T7A8DHVZN","aep",null,"The procedure for the lead agent of a WSO2 Labs Agentic Engineer CODING run. Do not load it in a subagent, or to write specs\u002F in a design or requirements turn.","wso2\u002Flabs-agentic-engineer","wso2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F533043?v=4","01M6CDAFS40T9Y86DYXWE0NJES","WSO2","01M735EE4N2PP2ZR56AX7DNPNP",24,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: aep\ndescription: The procedure for the lead agent of a WSO2 Labs Agentic Engineer CODING run. Do not load it in a subagent, or to write specs\u002F in a design or requirements turn.\nmetadata:\n  aep:\n    kind: platform\n    audience: [coding]\n---\n\n# AEP coding run\n\nYou are the lead agent. You work the open issues of one WSO2 Labs Agentic\nEngineer project. The current working directory is the project. You report\nnothing to the platform: the result is what you leave in the repo.\n\nTerms in this skill:\n\n- Run: this session. One run is one cycle of the milestone that your prompt\n  names.\n- Working set: the open issues that this run works.\n- Build issue: the one `development` issue of the milestone. Its body is the\n  checklist of the build.\n- Item: one line of that checklist, `- [ ] **\u003Citem>** …`. `\u003Citem>` is\n  `foundation`, a feature (`F2`) or `spec`. A ticked line (`- [x]`) is a done\n  item.\n- Build subagent: a subagent that builds the part of one item in one\n  component.\n- Wave: the build subagents of one item, which you dispatch together.\n- Green: a component that passes its verify step. The component contract\n  defines it.\n\n## Where you are\n\nThe working directory is a fresh clone of the GitHub repo of the project, on\nits default branch. Your prompt names a milestone, with a number and a title.\nThe record of the run is what you push and the pull request (PR) that you open.\n\n`git` and `gh` are already authenticated. Do not run `gh auth login`, do not\nset a token, and do not edit the credential helper. If a `git` or `gh` command\nfails to authenticate, it is a platform fault. Say so in one line and stop the\nrun.\n\n## This skill, and the stack skills\n\nRead `references\u002Fcomponent-contract.md` at the start of the run. It is the\nprocedure of the agent that builds a component: a build subagent, or you when\nyou work an issue inline.\n\nA stack skill owns the layout, the `Dockerfile`, the libraries and the verify\ncommand of one stack. The `design.json` of a component lists its stack skills\nin `skillsPinned`. Your skill catalog shows each name with a kind prefix: for\nexample, `ballerina` in `skillsPinned` is the skill `org-ballerina`. Load these\nskills before you write the code of the component.\n\n## Contract-first\n\nThe design wrote `specs\u002F` before the issues: the `design.json` of each\ncomponent, and the `openapi.yaml` of each service. These files are the\ncontract. Only you edit them, and only `openapi.yaml`, to close a gap that you\nor a build subagent find. Keep the change consistent with `security.json`: the\nIdP already has its scopes, and the gateway reads the `security` of each\noperation from `openapi.yaml`. Do not add a scope, change the scope of an\noperation, or remove an operation. A gap that you cannot close goes into the\nPR; do not work around it in code. Commit the change alone. Build again each\ncomponent that it touches, and list the change in the PR.\n\nA consumer codes against the `openapi.yaml` of its provider, not against the\ncode of the provider. As a result, the components of one item do not wait for\neach other: build them at the same time. The items go one after the other, in\nthe order of the checklist, because a later item builds on the code of the\nearlier ones.\n\n# The run\n\n## 1 · Start the cycle\n\nDo these steps before your first edit.\n\n### The set\n\nGet the working set from the issues API:\n\n```bash\ngh issue list --milestone \"\u003Cmilestone title>\" --state open \\\n  --json number,title,labels,url --limit 200\n```\n\n**Do not use the search API** (`gh search issues`, `gh api \u002Fsearch\u002F...`). Its\nindex is late, and it can miss the issue that started this run.\n\nThe working set is each open issue that has the `aep` label and one of these\nkind labels, or no kind label:\n\n| Kind label | Meaning | In the working set |\n|---|---|---|\n| `development` | planned work from the spec | yes |\n| `bug` | a red build, a failed deploy, a failed criterion, or a report from a person | yes |\n| `conflict` | a PR of yours that does not merge | yes |\n| `validation` | the check of the deployed system | no: a different run works it |\n| `provision` | a platform gate | no: do not touch it |\n\nAn issue without the `aep` label is a ledger issue. Do not work it, comment on\nit, or refer to it.\n\nIf `gh` says \"no milestone found\", the milestone is closed and the version is\nfinished. The working set is empty: go to Finish the cycle.\n\nRead the body and the comments of each issue in the working set. Work the\n`bug` and `conflict` issues first, in ascending number: they repair what is\nalready merged. Then work the items of the build issue, from the top. Skip a\nticked item.\n\nGet the working set again before you start the next issue or item. New issues\ncan arrive during the run.\n\n### Establish branch identity\n\nThe platform does not make your branch. Find it in this order:\n\n1. If a `conflict` issue names a PR, the head branch of that PR is your branch.\n   Rebase it on `origin\u002Fmain`. Resolve each conflict from the meaning of both\n   changes. Verify, then `git push --force-with-lease`.\n2. If an unmerged remote branch `aep\u002Fm\u003Cmilestone#>-*` exists, an earlier run\n   stopped. Check out that branch. Each of its commit messages ends with\n   `(#N)`, or `(#N \u003Citem>)` for an item: skip these issues and items. Tick a\n   skipped item that is not ticked yet.\n3. If not, make the branch `aep\u002Fm\u003Cmilestone#>-c\u003Ck>`. `\u003Ck>` is one more than the\n   highest `-c\u003Ck>` of this milestone, or 1. The platform finds your run from\n   this prefix.\n\n## 2 · Work the issues\n\nWork one bug or conflict issue, or one item of the build issue, at a time.\nFirst, put each of them in the task list, one entry each, in the order that you\nwill work them. The person who watches the run reads its progress there. Then,\nfor each:\n\n1. Read what it asks. For an item, read its feature file\n   (`specs\u002Frequirements\u002Ffeatures\u002FF\u003Cn>-*.md`) and its line in the checklist; for\n   Foundation, `specs\u002Frequirements\u002Fproduct-wide.md` and the design. Find the\n   screens, flows and operations that serve its stories. For a web\n   application, these include its prototype\n   (`specs\u002Fdesign\u002Fcomponents\u002F\u003Cc>\u002Fprototype.json` and `prototype.tsx`) and\n   `prototype`'s `references\u002Fimplementing.md`.\n2. Resolve the dependencies that only you can resolve (see Dependencies that\n   only you can resolve).\n3. Mark its task-list entry in progress. Then dispatch its wave: one build\n   subagent for each component that it names (see Fan-out to subagents).\n4. When a report arrives, do the steps in When a report arrives.\n5. When it is committed and ticked, mark its task-list entry completed. Get\n   the working set again, and start the next one.\n\nA wave builds its own item and nothing more. Do not give it work of a later\nitem, not even to make a component build or look complete sooner: the later\nitem's wave adds that work. A component that Foundation sets up has its setup,\nits wiring and its sign-in, and no feature yet. It must build and start like\nthat.\n\n### Fan-out to subagents\n\nThe tool glossary at the end of your instructions names your fan-out tool. Use\na build subagent for each component of the item, except:\n\n- Work a small fix inline.\n\nDo not name a model in the fan-out call.\n\nDispatch every build subagent of a wave in the background, in ONE turn, in\nthis one workspace (no worktrees). Then end your turn. Each subagent wakes you with its report when it finishes.\n\n**Only the commit waits for the whole item.** A subagent that did not report\ncan still be writing files.\n\n#### The build prompt\n\nA build subagent knows only its prompt. Give it these items, as paths and not\nas file contents. Do not change the component contract in the prompt:\n\n1. The issue number, the item, and the App Path of its component. The\n   subagent writes only in this path.\n2. What to build: for an item, its feature file and its story IDs, or for\n   Foundation the P items and the setup; the screens, flows and operations of\n   this component that serve them. For a web application, also its prototype\n   (`specs\u002Fdesign\u002Fcomponents\u002F\u003Cc>\u002Fprototype.json` and `prototype.tsx`) and\n   `prototype`'s `references\u002Fimplementing.md`. Tell the subagent to build only what the\n   item needs in this component, on top of the code that is there. For a bug\n   or conflict issue, the issue.\n3. The absolute path of `references\u002Fcomponent-contract.md`, exactly as your\n   prompt gives it. Tell the subagent: \"read this first; it is your contract\".\n4. The skills to load: each name in the `skillsPinned` of its component, with\n   its prefix.\n5. The data that you resolved: the `## Component \u003Cits name>` block of a\n   \"Platform-resolved dependencies\" comment, and each `org-service` contract\n   (pasted, as a path, or \"undocumented\").\n6. Its issue's status line: the `gh issue comment` command with its issue\n   number, and the rule in The status line.\n   That command is the only `gh` it may run.\n\n### Dependencies that only you can resolve\n\nThe build subagent writes the `workload.yaml` of its component from\n`references\u002Fworkload-and-wiring.md`. It cannot find the address of an\n`org-service`, which is a service of a different project. You give it.\n\n#### The `endpoints:` half\n\nThe platform posts a \"Platform-resolved dependencies\" comment on an issue of\nthe working set. The comment can be on a different issue than the issue of its\ncomponent. Each `## Component \u003Cname>` block in it goes, without a change, into\nthe `workload.yaml` of that component: through the build prompt, or by you. If\ntwo blocks name the same component, use the newest block.\n\n#### Finding an `org-service` contract\n\nThe \"Consumed API contracts\" sections of the comment name the providers. Call\n`list_org_component_endpoints` and find the row of the provider. Its\n`spec.availability` is one of these values:\n\n- `inline`: the document is in `spec.inlineContent`.\n- `repo`: read the document with `search_remote_git_code` and\n  `get_remote_git_file_contents`, in the `subdir` of the row.\n- `none`: there is no document.\n\n### When a report arrives\n\nTrust a report that says that the build is clean. Read again only the parts\nthat the report calls incomplete.\n\n1. A `web-application` is finished by a walk, not a build. Once its build\n   subagent reports clean and no other walk is live, dispatch one more subagent\n   for that component, with exactly this prompt:\n\n   ```text\n   Walk \u003Ccomponent> at \u003CApp Path> for \u003Citem>: walk only the prototype flows\n   that serve its stories (\u003Cstory IDs>), and the flows of earlier items. Load\n   `mock-verification` and `agent-browser`; the first is the whole procedure.\n   Edit\u002FWrite only inside\n   \u003CApp Path>; never run `git`. Progress: `gh issue comment \u003CN> --body \"\u003Cline>\"`.\n   Report back the closing line and the numbered list.\n   ```\n\n   Run only one walk at a time, because the browser uses the most memory in the\n   pod. Do not walk if the item changed no file that the app loads. Always\n   walk if you tick an item as \"already satisfied\".\n\n   If the walk report has open `[ ]` lines, the walk did not fail (see Walks in\n   the component contract). Commit the component, and copy the lines into the\n   PR.\n2. Commit the work of the item, alone, in one commit. You are the only agent\n   that runs `git`.\n   ```bash\n   git add \u003Cthe App Paths that the item touched>\n   git diff --cached --name-only    # what is ACTUALLY staged — read it\n   git commit -m \"\u003Ctype>: \u003Cshort summary> (#\u003Cnumber> \u003Citem>)\"   # a bug: (#\u003Cnumber>)\n   git push -u origin HEAD          # -u only on the first push\n   ```\n   A restart finds the done items from `(#N \u003Citem>)`, so push after each item.\n3. Tick the item in the build issue, after the push:\n   ```bash\n   gh issue view \u003Cnumber> --json body -q .body > \u002Ftmp\u002Fbuild-issue.md\n   # change only `- [ ] **\u003Citem>**` to `- [x] **\u003Citem>**`\n   gh issue edit \u003Cnumber> --body-file \u002Ftmp\u002Fbuild-issue.md\n   ```\n   The platform counts the ticks as the progress of the run.\n\n   `git add` does not add ignored files, and it gives no error. Compare the\n   staged list with the files that you changed.\n\n   You own the repo-root `.gitignore`. Read `references\u002Frepo-gitignore.md`\n   before you edit it, and before your first commit if the file does not start\n   with the `# crash artefacts` block.\n\nBefore you delete or rewrite a file that exists, write the reason in one\n`echo`. Only tool calls go to the progress feed, and a deletion with no reason\nlooks like an error.\n\n### The status line\n\nThe newest comment on an issue is its status line. The console shows its\nfirst line. The agent that works the issue posts one line:\n\n- when the work starts,\n- when the status changes (for example, a component becomes green, or the work\n  is committed),\n- when the work ends.\n\n```bash\ngh issue comment \u003Cnumber> --body \"\u003Cone line: what is happening on this issue now>\"\n```\n\nStart the line with the item. Example:\n`F2: todo-api builds clean; todo-web builds clean, walk dispatched.`\nComment only on the issue that you work. A walk posts its progress on the same\nissue, in the shapes that `mock-verification` gives. These comments can have\nmore than one line.\n\n## 3 · Finish the cycle\n\nWork that you cannot finish stays open for a later run. This is correct.\n\n### The record\n\nOpen one PR for the run. Put a `Resolves #N` line for each bug or conflict\nissue that you completed, and for the build issue when every item is ticked.\nWhen items of the build issue are still open, put `Advances #N` for it:\nGitHub does not close it, and the next run works the open items.\n\n```bash\ngh pr create \\\n  --title \"\u003Cshort summary of the cycle>\" \\\n  --body $'Resolves #12\\nAdvances #10\\n\\n\u003Cwhat changed, per item>'\n```\n\nThe platform merges the PR if it resolves or advances one or more agent-work\nissues of this milestone. GitHub then closes the issues listed with\n`Resolves`. If you do not list an issue that you finished, the next run works\nit again.\n\nAdd these parts to the PR when they apply:\n\n- For each item: what changed, by component, and for a web application the\n  walk's result. Put each open `[ ]` line of the walk report next to its\n  item.\n- For each spec change: the file, the change, and the gap that it closes.\n- For a component that is not green: list `Resolves #N` only for the\n  completed issues. Add an `## Error` section (the last 40 lines of output,\n  fenced) and a `## What was tried` section. When one or more items are\n  committed and ticked, open a usual PR with `Advances #N`: the platform does\n  not merge a draft. Use `--draft` and the title prefix `[build-failed]` only\n  when the cycle completed no item and no issue.\n\nKeep each unfinished issue open. Make its last status line the same\ndiagnostic.\n\n### Be idempotent\n\nThe run can be a restart of a run that stopped:\n\n- If work is pushed and no PR is open, open the PR. Put a `Resolves` line for\n  each `(#N)` in `git log origin\u002Fmain..HEAD`, and the build issue's line from\n  its ticks (see The record).\n- If a PR is open and the working set is empty, rewrite its body with\n  `gh pr edit \u003Cnumber> --body ...`. Put a `Resolves #N` line for each `(#N)` on\n  the branch and the build issue's line from its ticks, keep the rest of the body, and make the last line\n  `Adopted: \u003Cdate -u +%Y-%m-%dT%H:%M:%SZ>`. Replace an earlier `Adopted:` line.\n  Rewrite the body also when the list is complete: this edit is how the\n  platform learns that the cycle waits for the PR, and the new `Adopted:` line\n  makes sure that the body changes. Then stop. Do not open a second PR.\n- If the working set is empty and nothing is pushed, stop and say so.\n\n# Never\n\n`references\u002Fcomponent-contract.md` gives the rules for each agent that changes\nfiles. This rule is for the run:\n\n- Do not let a subagent run `git`, or any `gh` its prompt did not give it.\n\n## Git and GitHub\n\n- Do not push to `main`. Push only to the `aep\u002Fm\u003Cmilestone#>-…` branch of the\n  run.\n- Do not force-push, except to your branch after a conflict rebase. Then use\n  only `--force-with-lease`.\n- Do not run `gh pr merge`, `gh pr close`, `gh repo create`,\n  `gh repo delete`, `gh repo fork` or `gh repo edit`.\n- Do not delete remote branches.\n- Do not change branch protection, secrets, repository settings,\n  collaborators or webhooks.\n","# AEP coding run\n\nYou are the lead agent. You work the open issues of one WSO2 Labs Agentic\nEngineer project. The current working directory is the project. You report\nnothing to the platform: the result is what you leave in the repo.\n\nTerms in this skill:\n\n- Run: this session. One run is one cycle of the milestone that your prompt\n  names.\n- Working set: the open issues that this run works.\n- Build issue: the one `development` issue of the milestone. Its body is the\n  checklist of the build.\n- Item: one line of that checklist, `- [ ] **\u003Citem>** …`. `\u003Citem>` is\n  `foundation`, a feature (`F2`) or `spec`. A ticked line (`- [x]`) is a done\n  item.\n- Build subagent: a subagent that builds the part of one item in one\n  component.\n- Wave: the build subagents of one item, which you dispatch together.\n- Green: a component that passes its verify step. The component contract\n  defines it.\n\n## Where you are\n\nThe working directory is a fresh clone of the GitHub repo of the project, on\nits default branch. Your prompt names a milestone, with a number and a title.\nThe record of the run is what you push and the pull request (PR) that you open.\n\n`git` and `gh` are already authenticated. Do not run `gh auth login`, do not\nset a token, and do not edit the credential helper. If a `git` or `gh` command\nfails to authenticate, it is a platform fault. Say so in one line and stop the\nrun.\n\n## This skill, and the stack skills\n\nRead `references\u002Fcomponent-contract.md` at the start of the run. It is the\nprocedure of the agent that builds a component: a build subagent, or you when\nyou work an issue inline.\n\nA stack skill owns the layout, the `Dockerfile`, the libraries and the verify\ncommand of one stack. The `design.json` of a component lists its stack skills\nin `skillsPinned`. Your skill catalog shows each name with a kind prefix: for\nexample, `ballerina` in `skillsPinned` is the skill `org-ballerina`. Load these\nskills before you write the code of the component.\n\n## Contract-first\n\nThe design wrote `specs\u002F` before the issues: the `design.json` of each\ncomponent, and the `openapi.yaml` of each service. These files are the\ncontract. Only you edit them, and only `openapi.yaml`, to close a gap that you\nor a build subagent find. Keep the change consistent with `security.json`: the\nIdP already has its scopes, and the gateway reads the `security` of each\noperation from `openapi.yaml`. Do not add a scope, change the scope of an\noperation, or remove an operation. A gap that you cannot close goes into the\nPR; do not work around it in code. Commit the change alone. Build again each\ncomponent that it touches, and list the change in the PR.\n\nA consumer codes against the `openapi.yaml` of its provider, not against the\ncode of the provider. As a result, the components of one item do not wait for\neach other: build them at the same time. The items go one after the other, in\nthe order of the checklist, because a later item builds on the code of the\nearlier ones.\n\n# The run\n\n## 1 · Start the cycle\n\nDo these steps before your first edit.\n\n### The set\n\nGet the working set from the issues API:\n\n```bash\ngh issue list --milestone \"\u003Cmilestone title>\" --state open \\\n  --json number,title,labels,url --limit 200\n```\n\n**Do not use the search API** (`gh search issues`, `gh api \u002Fsearch\u002F...`). Its\nindex is late, and it can miss the issue that started this run.\n\nThe working set is each open issue that has the `aep` label and one of these\nkind labels, or no kind label:\n\n| Kind label | Meaning | In the working set |\n|---|---|---|\n| `development` | planned work from the spec | yes |\n| `bug` | a red build, a failed deploy, a failed criterion, or a report from a person | yes |\n| `conflict` | a PR of yours that does not merge | yes |\n| `validation` | the check of the deployed system | no: a different run works it |\n| `provision` | a platform gate | no: do not touch it |\n\nAn issue without the `aep` label is a ledger issue. Do not work it, comment on\nit, or refer to it.\n\nIf `gh` says \"no milestone found\", the milestone is closed and the version is\nfinished. The working set is empty: go to Finish the cycle.\n\nRead the body and the comments of each issue in the working set. Work the\n`bug` and `conflict` issues first, in ascending number: they repair what is\nalready merged. Then work the items of the build issue, from the top. Skip a\nticked item.\n\nGet the working set again before you start the next issue or item. New issues\ncan arrive during the run.\n\n### Establish branch identity\n\nThe platform does not make your branch. Find it in this order:\n\n1. If a `conflict` issue names a PR, the head branch of that PR is your branch.\n   Rebase it on `origin\u002Fmain`. Resolve each conflict from the meaning of both\n   changes. Verify, then `git push --force-with-lease`.\n2. If an unmerged remote branch `aep\u002Fm\u003Cmilestone#>-*` exists, an earlier run\n   stopped. Check out that branch. Each of its commit messages ends with\n   `(#N)`, or `(#N \u003Citem>)` for an item: skip these issues and items. Tick a\n   skipped item that is not ticked yet.\n3. If not, make the branch `aep\u002Fm\u003Cmilestone#>-c\u003Ck>`. `\u003Ck>` is one more than the\n   highest `-c\u003Ck>` of this milestone, or 1. The platform finds your run from\n   this prefix.\n\n## 2 · Work the issues\n\nWork one bug or conflict issue, or one item of the build issue, at a time.\nFirst, put each of them in the task list, one entry each, in the order that you\nwill work them. The person who watches the run reads its progress there. Then,\nfor each:\n\n1. Read what it asks. For an item, read its feature file\n   (`specs\u002Frequirements\u002Ffeatures\u002FF\u003Cn>-*.md`) and its line in the checklist; for\n   Foundation, `specs\u002Frequirements\u002Fproduct-wide.md` and the design. Find the\n   screens, flows and operations that serve its stories. For a web\n   application, these include its prototype\n   (`specs\u002Fdesign\u002Fcomponents\u002F\u003Cc>\u002Fprototype.json` and `prototype.tsx`) and\n   `prototype`'s `references\u002Fimplementing.md`.\n2. Resolve the dependencies that only you can resolve (see Dependencies that\n   only you can resolve).\n3. Mark its task-list entry in progress. Then dispatch its wave: one build\n   subagent for each component that it names (see Fan-out to subagents).\n4. When a report arrives, do the steps in When a report arrives.\n5. When it is committed and ticked, mark its task-list entry completed. Get\n   the working set again, and start the next one.\n\nA wave builds its own item and nothing more. Do not give it work of a later\nitem, not even to make a component build or look complete sooner: the later\nitem's wave adds that work. A component that Foundation sets up has its setup,\nits wiring and its sign-in, and no feature yet. It must build and start like\nthat.\n\n### Fan-out to subagents\n\nThe tool glossary at the end of your instructions names your fan-out tool. Use\na build subagent for each component of the item, except:\n\n- Work a small fix inline.\n\nDo not name a model in the fan-out call.\n\nDispatch every build subagent of a wave in the background, in ONE turn, in\nthis one workspace (no worktrees). Then end your turn. Each subagent wakes you with its report when it finishes.\n\n**Only the commit waits for the whole item.** A subagent that did not report\ncan still be writing files.\n\n#### The build prompt\n\nA build subagent knows only its prompt. Give it these items, as paths and not\nas file contents. Do not change the component contract in the prompt:\n\n1. The issue number, the item, and the App Path of its component. The\n   subagent writes only in this path.\n2. What to build: for an item, its feature file and its story IDs, or for\n   Foundation the P items and the setup; the screens, flows and operations of\n   this component that serve them. For a web application, also its prototype\n   (`specs\u002Fdesign\u002Fcomponents\u002F\u003Cc>\u002Fprototype.json` and `prototype.tsx`) and\n   `prototype`'s `references\u002Fimplementing.md`. Tell the subagent to build only what the\n   item needs in this component, on top of the code that is there. For a bug\n   or conflict issue, the issue.\n3. The absolute path of `references\u002Fcomponent-contract.md`, exactly as your\n   prompt gives it. Tell the subagent: \"read this first; it is your contract\".\n4. The skills to load: each name in the `skillsPinned` of its component, with\n   its prefix.\n5. The data that you resolved: the `## Component \u003Cits name>` block of a\n   \"Platform-resolved dependencies\" comment, and each `org-service` contract\n   (pasted, as a path, or \"undocumented\").\n6. Its issue's status line: the `gh issue comment` command with its issue\n   number, and the rule in The status line.\n   That command is the only `gh` it may run.\n\n### Dependencies that only you can resolve\n\nThe build subagent writes the `workload.yaml` of its component from\n`references\u002Fworkload-and-wiring.md`. It cannot find the address of an\n`org-service`, which is a service of a different project. You give it.\n\n#### The `endpoints:` half\n\nThe platform posts a \"Platform-resolved dependencies\" comment on an issue of\nthe working set. The comment can be on a different issue than the issue of its\ncomponent. Each `## Component \u003Cname>` block in it goes, without a change, into\nthe `workload.yaml` of that component: through the build prompt, or by you. If\ntwo blocks name the same component, use the newest block.\n\n#### Finding an `org-service` contract\n\nThe \"Consumed API contracts\" sections of the comment name the providers. Call\n`list_org_component_endpoints` and find the row of the provider. Its\n`spec.availability` is one of these values:\n\n- `inline`: the document is in `spec.inlineContent`.\n- `repo`: read the document with `search_remote_git_code` and\n  `get_remote_git_file_contents`, in the `subdir` of the row.\n- `none`: there is no document.\n\n### When a report arrives\n\nTrust a report that says that the build is clean. Read again only the parts\nthat the report calls incomplete.\n\n1. A `web-application` is finished by a walk, not a build. Once its build\n   subagent reports clean and no other walk is live, dispatch one more subagent\n   for that component, with exactly this prompt:\n\n   ```text\n   Walk \u003Ccomponent> at \u003CApp Path> for \u003Citem>: walk only the prototype flows\n   that serve its stories (\u003Cstory IDs>), and the flows of earlier items. Load\n   `mock-verification` and `agent-browser`; the first is the whole procedure.\n   Edit\u002FWrite only inside\n   \u003CApp Path>; never run `git`. Progress: `gh issue comment \u003CN> --body \"\u003Cline>\"`.\n   Report back the closing line and the numbered list.\n   ```\n\n   Run only one walk at a time, because the browser uses the most memory in the\n   pod. Do not walk if the item changed no file that the app loads. Always\n   walk if you tick an item as \"already satisfied\".\n\n   If the walk report has open `[ ]` lines, the walk did not fail (see Walks in\n   the component contract). Commit the component, and copy the lines into the\n   PR.\n2. Commit the work of the item, alone, in one commit. You are the only agent\n   that runs `git`.\n   ```bash\n   git add \u003Cthe App Paths that the item touched>\n   git diff --cached --name-only    # what is ACTUALLY staged — read it\n   git commit -m \"\u003Ctype>: \u003Cshort summary> (#\u003Cnumber> \u003Citem>)\"   # a bug: (#\u003Cnumber>)\n   git push -u origin HEAD          # -u only on the first push\n   ```\n   A restart finds the done items from `(#N \u003Citem>)`, so push after each item.\n3. Tick the item in the build issue, after the push:\n   ```bash\n   gh issue view \u003Cnumber> --json body -q .body > \u002Ftmp\u002Fbuild-issue.md\n   # change only `- [ ] **\u003Citem>**` to `- [x] **\u003Citem>**`\n   gh issue edit \u003Cnumber> --body-file \u002Ftmp\u002Fbuild-issue.md\n   ```\n   The platform counts the ticks as the progress of the run.\n\n   `git add` does not add ignored files, and it gives no error. Compare the\n   staged list with the files that you changed.\n\n   You own the repo-root `.gitignore`. Read `references\u002Frepo-gitignore.md`\n   before you edit it, and before your first commit if the file does not start\n   with the `# crash artefacts` block.\n\nBefore you delete or rewrite a file that exists, write the reason in one\n`echo`. Only tool calls go to the progress feed, and a deletion with no reason\nlooks like an error.\n\n### The status line\n\nThe newest comment on an issue is its status line. The console shows its\nfirst line. The agent that works the issue posts one line:\n\n- when the work starts,\n- when the status changes (for example, a component becomes green, or the work\n  is committed),\n- when the work ends.\n\n```bash\ngh issue comment \u003Cnumber> --body \"\u003Cone line: what is happening on this issue now>\"\n```\n\nStart the line with the item. Example:\n`F2: todo-api builds clean; todo-web builds clean, walk dispatched.`\nComment only on the issue that you work. A walk posts its progress on the same\nissue, in the shapes that `mock-verification` gives. These comments can have\nmore than one line.\n\n## 3 · Finish the cycle\n\nWork that you cannot finish stays open for a later run. This is correct.\n\n### The record\n\nOpen one PR for the run. Put a `Resolves #N` line for each bug or conflict\nissue that you completed, and for the build issue when every item is ticked.\nWhen items of the build issue are still open, put `Advances #N` for it:\nGitHub does not close it, and the next run works the open items.\n\n```bash\ngh pr create \\\n  --title \"\u003Cshort summary of the cycle>\" \\\n  --body $'Resolves #12\\nAdvances #10\\n\\n\u003Cwhat changed, per item>'\n```\n\nThe platform merges the PR if it resolves or advances one or more agent-work\nissues of this milestone. GitHub then closes the issues listed with\n`Resolves`. If you do not list an issue that you finished, the next run works\nit again.\n\nAdd these parts to the PR when they apply:\n\n- For each item: what changed, by component, and for a web application the\n  walk's result. Put each open `[ ]` line of the walk report next to its\n  item.\n- For each spec change: the file, the change, and the gap that it closes.\n- For a component that is not green: list `Resolves #N` only for the\n  completed issues. Add an `## Error` section (the last 40 lines of output,\n  fenced) and a `## What was tried` section. When one or more items are\n  committed and ticked, open a usual PR with `Advances #N`: the platform does\n  not merge a draft. Use `--draft` and the title prefix `[build-failed]` only\n  when the cycle completed no item and no issue.\n\nKeep each unfinished issue open. Make its last status line the same\ndiagnostic.\n\n### Be idempotent\n\nThe run can be a restart of a run that stopped:\n\n- If work is pushed and no PR is open, open the PR. Put a `Resolves` line for\n  each `(#N)` in `git log origin\u002Fmain..HEAD`, and the build issue's line from\n  its ticks (see The record).\n- If a PR is open and the working set is empty, rewrite its body with\n  `gh pr edit \u003Cnumber> --body ...`. Put a `Resolves #N` line for each `(#N)` on\n  the branch and the build issue's line from its ticks, keep the rest of the body, and make the last line\n  `Adopted: \u003Cdate -u +%Y-%m-%dT%H:%M:%SZ>`. Replace an earlier `Adopted:` line.\n  Rewrite the body also when the list is complete: this edit is how the\n  platform learns that the cycle waits for the PR, and the new `Adopted:` line\n  makes sure that the body changes. Then stop. Do not open a second PR.\n- If the working set is empty and nothing is pushed, stop and say so.\n\n# Never\n\n`references\u002Fcomponent-contract.md` gives the rules for each agent that changes\nfiles. This rule is for the run:\n\n- Do not let a subagent run `git`, or any `gh` its prompt did not give it.\n\n## Git and GitHub\n\n- Do not push to `main`. Push only to the `aep\u002Fm\u003Cmilestone#>-…` branch of the\n  run.\n- Do not force-push, except to your branch after a conflict rebase. Then use\n  only `--force-with-lease`.\n- Do not run `gh pr merge`, `gh pr close`, `gh repo create`,\n  `gh repo delete`, `gh repo fork` or `gh repo edit`.\n- Do not delete remote branches.\n- Do not change branch protection, secrets, repository settings,\n  collaborators or webhooks.\n",{"name":5,"metadata":24,"description":7},{"aep":25},{"kind":26,"audience":27},"platform",[28],"coding","main","e3b5fc8668f26761380b2d4965719f2d8f2eb246","skills\u002Faep","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer","https:\u002F\u002Fgithub.com\u002Fwso2","https:\u002F\u002Fwso2.com","Welcome to the WSO2 source code! For info on working with the WSO2 repositories and contributing code, click the link below.","2026-11-11 15:36:27",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add wso2\u002Flabs-agentic-engineer --skill aep",{"tool":43,"command":44},"bunx","bunx skills add wso2\u002Flabs-agentic-engineer --skill aep",{"tool":46,"command":47},"pnpm","pnpm dlx skills add wso2\u002Flabs-agentic-engineer --skill aep","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002FSKILL.md",true,[51,57,61,65,69],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"overlays\u002Flocal.md","REFERENCE","参考文档",6348,"https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002Foverlays\u002Flocal.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcomponent-contract.md",7244,"https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002Freferences\u002Fcomponent-contract.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fexternal-dependency-research.md",2909,"https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002Freferences\u002Fexternal-dependency-research.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Frepo-gitignore.md",1067,"https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002Freferences\u002Frepo-gitignore.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fworkload-and-wiring.md",5121,"https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Faep\u002Freferences\u002Fworkload-and-wiring.md",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M735MP9NFFRPS260G9D16JQX","validation-task","Load when working a VALIDATION task dispatched by WSO2 Labs Agentic Engineer — judging a deployed version against its acceptance criteria.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fvalidation-task\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M735MJ8ZMRZR20A57TMF7R9Q","thunder-authentication","Apply when a component sits on the project's sign-in — a SPA whose users authenticate through the auth platform-resource dependency, or a protected backend those signed-in users call.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fthunder-authentication\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M735MFQMY8DY1EM7JKS784D3","task-planning","Use when planning a version's build from a design — the plan turn that writes the build's checklist with planBuild, one item per feature the version carries in build order, after a Foundation item when the version needs one.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Ftask-planning\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M735MCJQ4EVH7G4ZFMC682Y4","start","Use when kicking off a project from its idea — the product pass that agrees the feature list and writes the product page, the product-wide page and a stub per feature — or re-running \u002Fstart on a project that already has requirements.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fstart\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M735M9R050KT3H34PVXN2MKK","security-design","Write specs\u002Fdesign\u002Fsecurity.json when a design has sign-in, permissions, roles or test users — the permission catalog every API operation is gated on.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-design\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M735M60CTW4S7XMS6XCX9A7Y","resolve-dependency","Use for taking one external dependency from open to resolved — `\u002Fresolve-dependency \u003Cname> [answer]` names it and may carry the provider the user chose; `\u002Fresolve-dependencies` walks every open one in turn. Ask which provider (their suggestions as options; never choose for them), get its interface on disk (found, uploaded from the card, or assumed under the authorization the card records), then derive the config keys.","https:\u002F\u002Fgithub.com\u002Fwso2\u002Flabs-agentic-engineer\u002Fblob\u002Fmain\u002Fskills\u002Fresolve-dependency\u002FSKILL.md",[],[]]