[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M719MWFZMHDZDXVTGSHCF4ZW":3,"skill-same:01M719MWFZMHDZDXVTGSHCF4ZW":75},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M719MWFZMHDZDXVTGSHCF4ZW","lifecycle-agent-orchestrator-dry-run",null,"Dry-run mode for the lifecycle agent orchestrator. Simulates the full 9-phase pipeline against a sample or custom requirement without making any real changes — no files, no git, no Jira, no PRs. Use this to validate the orchestrator workflow, demonstrate the pipeline to new users, or test overlay integration. Trigger when the user says \"dry run\", \"simulate the lifecycle\", \"test the orchestrator\", or \"show me how the pipeline works\".","sandeep-mewara\u002Flifecycle-agent-orchestrator","sandeep-mewara","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22136242?v=4","01M719M4609V9R414KB797CMRG","Sandeep Mewara","01M719M4700Q6AQQYT5EE5Z2DG",1,"MIT","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Fskills\u002Flao-dry-run\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"orchestrator","run","lifecycle agent orchestrator dry run","lifecycle","agent orchestrator","dry","jira","how","me","sample","phase","workflow","show me","when","files","new","mode","pipeline","overlay","show","2026-11-10 10:12:30",false,"---\nname: lifecycle-agent-orchestrator-dry-run\naliases: [lao-dry-run]\ndescription: >\n  Dry-run mode for the lifecycle agent orchestrator. Simulates the full 9-phase pipeline against\n  a sample or custom requirement without making any real changes — no files, no git,\n  no Jira, no PRs. Use this to validate the orchestrator workflow, demonstrate the\n  pipeline to new users, or test overlay integration. Trigger when the user says\n  \"dry run\", \"simulate the lifecycle\", \"test the orchestrator\", or \"show me how the\n  pipeline works\".\n---\n\n# Lifecycle Agent Orchestrator — Dry Run\n\nYou are running the lifecycle agent orchestrator in **dry-run mode**. This validates the full\nworkflow end-to-end by simulating every phase and producing PhaseOutput at each\ncheckpoint — without making any actual changes.\n\n## Hard Rules\n\n- **NO file creation or modification** — do not write code, create plans, or save documents\n- **NO git operations** — do not create branches, make commits, or push\n- **NO Jira operations** — do not create tickets, transition statuses, or add comments\n- **NO PR creation** — do not push or create pull requests\n- **SIMULATED OUTPUT ONLY** — every phase produces a realistic PhaseOutput as if the work\n  was done, but nothing actually happens\n\n## Input\n\nIf the user provided a requirement, use that.\nOtherwise, read the bundled sample at `examples\u002Fsample-requirement.md` and use its requirement.\n\n## Process\n\nRead the orchestrator skill at `skills\u002Flao\u002FSKILL.md` and follow its\nphase pipeline exactly, but at each phase:\n\n1. **Announce the phase** — state which phase is running, which skill would be invoked\n2. **Simulate the work** — describe what the skill would do (don't actually do it)\n3. **Produce PhaseOutput** — render a realistic PhaseOutput per `contracts\u002Fphase-output-schema.md`\n   using the CLI rendering format. Include realistic but simulated content.\n4. **Present the checkpoint** — show the checkpoint to the user (combined checkpoints where\n   the orchestrator would combine them)\n5. **Wait for approval** — the user approves or requests changes, just like the real workflow\n6. **Proceed to next phase** — on approval, move to the next phase\n\n## What to Simulate at Each Phase\n\n**Phase 1 — Product Management:**\n- Simulate: PRD analysis, user story extraction, Jira ticket creation\n- Cross-review: XD (UX feasibility) + Architecture (tech feasibility)\n- Output: 2-3 user stories with acceptance criteria, ticket summary\n\n**Phase 2 — Experience Design, PRD Level (if UX needed):**\n- Simulate: Complete experience design across all tickets — journeys, screens, interactions, states\n- Cross-review: PM (requirements coverage) + Architecture (tech feasibility)\n- Output: Design deliverables summary with cross-review feedback\n\n**Phase 3 — Architecture, System Design:**\n- Simulate: System-level design, component boundaries, ADRs, dependency analysis, ticket ordering\n- Cross-review: PM (AC coverage) + XD (design support, if Phase 2 ran)\n- Output: System design summary + execution order recommendation\n\n**Phase 4 — Intake:**\n- Simulate: Scope extraction, AC numbering\n- Output: Scope summary with numbered ACs\n\n**Phase 5 — Tech Design:**\n- Simulate: Low-level technical approach within system architecture\n- Output: Design summary (no cross-review — purely technical)\n\n**Phase 6 — Plan:**\n- Simulate: Task breakdown\n- Output: 3-5 task summaries (no actual plan file)\n\n**Phase 7 — Implement:**\n- Simulate: TDD execution, spec review, quality review per task\n- Output: Task results table with all tasks passed\n\n**Phase 8 — Validate:**\n- Simulate: AC verification against \"implemented\" code\n- Output: AC status table (all pass with simulated evidence), test results\n\n**Phase 9 — Ship:**\n- Simulate: PR description, Jira transition\n- Output: Simulated PR summary and Jira update\n\n## Checkpoint Collapsing\n\nApply the same collapsing rules as the real orchestrator:\n- If the requirement produces a single backend ticket: 3 combined checkpoints (Phases 4-9)\n- If UX is involved: Phase 1, Phase 2 (XD), Phase 3 (system design), then per-ticket checkpoints\n- If complex with multiple tickets: full phase-by-phase checkpoints\n- All cross-reviews happen in Phases 1-3, per-ticket phases have no cross-review gates\n\n## At Completion\n\nAfter all phases, print:\n\n```\n=== Dry Run Complete ===\n\nPhases simulated: {N}\nCheckpoints presented: {N}\nEntry point detected: {A\u002FB\u002FC\u002FD}\nPhases skipped: {list or \"None\"}\nCross-reviews simulated: {N}\n\nThe lifecycle agent orchestrator workflow validated successfully.\nNo files were created, no branches, no Jira tickets, no PRs.\n```\n\n## Why This Exists\n\nThis standalone dry run serves three purposes:\n1. **Validate the plugin** — confirm all skills, contracts, and the orchestrator flow work\n2. **Demonstrate the workflow** — show users what the lifecycle pipeline looks like before using it on real work\n3. **Test overlay integration** — if project overlays exist, the dry run shows how they're composed with base skills\n\n**Note:** This is separate from the orchestrator's built-in preview phase. When you use\n`\u002Flao` on real work, it automatically starts with a preview before executing.\nThis standalone `\u002Flao-dry-run` is for demos, validation, and testing — it\nnever transitions to real execution.\n","# Lifecycle Agent Orchestrator — Dry Run\n\nYou are running the lifecycle agent orchestrator in **dry-run mode**. This validates the full\nworkflow end-to-end by simulating every phase and producing PhaseOutput at each\ncheckpoint — without making any actual changes.\n\n## Hard Rules\n\n- **NO file creation or modification** — do not write code, create plans, or save documents\n- **NO git operations** — do not create branches, make commits, or push\n- **NO Jira operations** — do not create tickets, transition statuses, or add comments\n- **NO PR creation** — do not push or create pull requests\n- **SIMULATED OUTPUT ONLY** — every phase produces a realistic PhaseOutput as if the work\n  was done, but nothing actually happens\n\n## Input\n\nIf the user provided a requirement, use that.\nOtherwise, read the bundled sample at `examples\u002Fsample-requirement.md` and use its requirement.\n\n## Process\n\nRead the orchestrator skill at `skills\u002Flao\u002FSKILL.md` and follow its\nphase pipeline exactly, but at each phase:\n\n1. **Announce the phase** — state which phase is running, which skill would be invoked\n2. **Simulate the work** — describe what the skill would do (don't actually do it)\n3. **Produce PhaseOutput** — render a realistic PhaseOutput per `contracts\u002Fphase-output-schema.md`\n   using the CLI rendering format. Include realistic but simulated content.\n4. **Present the checkpoint** — show the checkpoint to the user (combined checkpoints where\n   the orchestrator would combine them)\n5. **Wait for approval** — the user approves or requests changes, just like the real workflow\n6. **Proceed to next phase** — on approval, move to the next phase\n\n## What to Simulate at Each Phase\n\n**Phase 1 — Product Management:**\n- Simulate: PRD analysis, user story extraction, Jira ticket creation\n- Cross-review: XD (UX feasibility) + Architecture (tech feasibility)\n- Output: 2-3 user stories with acceptance criteria, ticket summary\n\n**Phase 2 — Experience Design, PRD Level (if UX needed):**\n- Simulate: Complete experience design across all tickets — journeys, screens, interactions, states\n- Cross-review: PM (requirements coverage) + Architecture (tech feasibility)\n- Output: Design deliverables summary with cross-review feedback\n\n**Phase 3 — Architecture, System Design:**\n- Simulate: System-level design, component boundaries, ADRs, dependency analysis, ticket ordering\n- Cross-review: PM (AC coverage) + XD (design support, if Phase 2 ran)\n- Output: System design summary + execution order recommendation\n\n**Phase 4 — Intake:**\n- Simulate: Scope extraction, AC numbering\n- Output: Scope summary with numbered ACs\n\n**Phase 5 — Tech Design:**\n- Simulate: Low-level technical approach within system architecture\n- Output: Design summary (no cross-review — purely technical)\n\n**Phase 6 — Plan:**\n- Simulate: Task breakdown\n- Output: 3-5 task summaries (no actual plan file)\n\n**Phase 7 — Implement:**\n- Simulate: TDD execution, spec review, quality review per task\n- Output: Task results table with all tasks passed\n\n**Phase 8 — Validate:**\n- Simulate: AC verification against \"implemented\" code\n- Output: AC status table (all pass with simulated evidence), test results\n\n**Phase 9 — Ship:**\n- Simulate: PR description, Jira transition\n- Output: Simulated PR summary and Jira update\n\n## Checkpoint Collapsing\n\nApply the same collapsing rules as the real orchestrator:\n- If the requirement produces a single backend ticket: 3 combined checkpoints (Phases 4-9)\n- If UX is involved: Phase 1, Phase 2 (XD), Phase 3 (system design), then per-ticket checkpoints\n- If complex with multiple tickets: full phase-by-phase checkpoints\n- All cross-reviews happen in Phases 1-3, per-ticket phases have no cross-review gates\n\n## At Completion\n\nAfter all phases, print:\n\n```\n=== Dry Run Complete ===\n\nPhases simulated: {N}\nCheckpoints presented: {N}\nEntry point detected: {A\u002FB\u002FC\u002FD}\nPhases skipped: {list or \"None\"}\nCross-reviews simulated: {N}\n\nThe lifecycle agent orchestrator workflow validated successfully.\nNo files were created, no branches, no Jira tickets, no PRs.\n```\n\n## Why This Exists\n\nThis standalone dry run serves three purposes:\n1. **Validate the plugin** — confirm all skills, contracts, and the orchestrator flow work\n2. **Demonstrate the workflow** — show users what the lifecycle pipeline looks like before using it on real work\n3. **Test overlay integration** — if project overlays exist, the dry run shows how they're composed with base skills\n\n**Note:** This is separate from the orchestrator's built-in preview phase. When you use\n`\u002Flao` on real work, it automatically starts with a preview before executing.\nThis standalone `\u002Flao-dry-run` is for demos, validation, and testing — it\nnever transitions to real execution.\n",{"name":5,"aliases":49,"description":7},[50],"lao-dry-run","main","7df021855a805acbcdc470d3b4419009e57f0330","plugins\u002Flifecycle-agent-orchestrator\u002Fskills\u002Flao-dry-run",0,"https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator","https:\u002F\u002Flearnbyinsight.com\u002F2026\u002F04\u002F19\u002Fthe-lifecycle-is-the-product-ai-development-engine\u002F","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara","https:\u002F\u002Flearnbyinsight.com\u002F","A software professional for more than 15+ years learning ...","2026-04-20 00:49:35",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add sandeep-mewara\u002Flifecycle-agent-orchestrator --skill lifecycle-agent-orchestrator-dry-run",{"tool":67,"command":68},"bunx","bunx skills add sandeep-mewara\u002Flifecycle-agent-orchestrator --skill lifecycle-agent-orchestrator-dry-run",{"tool":70,"command":71},"pnpm","pnpm dlx skills add sandeep-mewara\u002Flifecycle-agent-orchestrator --skill lifecycle-agent-orchestrator-dry-run","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Fskills\u002Flao-dry-run\u002FSKILL.md",true,[],[76,94,113,120,147,169],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":44},"01M719NW8TNRJGM3T22XC1HS1Y","extra-role","A custom project-specific role for testing","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Ftests\u002Ffixtures\u002Fvalid-project\u002Fextra-role\u002FSKILL.md",[],[83,84,85,86,87,88,89,90,91,92,93],"role","extra","extra role","review","architecture","code-review","code","for","project","testing","custom",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":105,"publishedAt":44},"01M719NTA6SXBZ2VG2YX7PT1G8","compliance-review","Ensures regulatory compliance for financial services","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Ftests\u002Ffixtures\u002Fvalid-config\u002Ftools\u002Fcompliance\u002FSKILL.md",[100],{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[106,107,86,108,87,88,89,109,110,111,90,112],"compliance","compliance review","financial services","security","regulatory compliance","regulatory","services",{"skillNo":114,"name":78,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":44},"01M719NS3WX4TRDAX41V5PSSF2","A custom role missing applies_to for testing","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Ftests\u002Ffixtures\u002Fmissing-applies-to-extra\u002Fextra-role\u002FSKILL.md",[],[83,85,84,90,93,119,92],"missing",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":130,"publishedAt":44},"01M719NMWH7M49CSX17DBJYCE1","testing-conventions","Enforces testing standards when writing unit tests, integration tests, or agent evaluation tests. Covers test directory structure, naming conventions, fixture and setup patterns, mocking strategy, async testing, coverage requirements, and LLM-as-judge evaluation. Language-specific conventions (Python\u002Fpytest, Java\u002FJUnit, C#\u002FxUnit, React\u002FVitest) are loaded from bundled reference packs. Use this skill when writing tests, creating test files, setting up fixtures, mocking services, or reviewing test code for standards compliance.","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Fskills\u002Ftesting-conventions\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[131,132,92,133,89,134,135,37,136,137,138,139,140,141,38,142,143,144,145,146],"conventions","testing conventions","testing standards","react","structure","directory","LLM-as-Judge","Evaluation","judge","patterns","pytest","up","fixture","unit","coverage","writing",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":44},"01M719NGZVGA0C0NY8G66FNHB8","shipping","Shipping workflow for platform services. Use this skill when creating pull requests, pushing code for review, updating Jira tickets to reflect PR status, or completing the ship cycle for a feature or bugfix. Trigger this skill when the user says things like \"open a PR,\" \"create a pull request,\" \"ship this,\" \"push for review,\" \"update the ticket,\" \"mark this as ready for review,\" or \"I'm done with this feature\" — even if they don't explicitly say \"shipping.\" Also trigger when the user wants to transition a Jira ticket status after code changes are ready.","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Fskills\u002Fshipping\u002FSKILL.md",[153],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[149,155,156,157,158,159,160,161,30,162,163,164,165,166,86,167,89,168,35,37],"ticket","cycle","ready","open","transition","status","bugfix","update","request","pull requests","reflect","create","creating pull requests","done",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":180,"publishedAt":44},"01M719NCJ3BNN5AXQ1V1FDYCJS","security-standards","Enforces security standards when writing or reviewing code that handles authentication, secrets, sensitive data, API boundaries, or compliance concerns. Covers secrets manager integration, encryption at rest and in transit, IAM authentication and least-privilege authorization, OWASP Top 10 secure coding (including prompt injection), dependency vulnerability management, API security (auth, validation, rate limiting), PII and sensitive data protection in logs and traces, and regulatory compliance (CCPA\u002FGDPR). Use this skill when adding endpoints, handling user data, managing secrets, reviewing for vulnerabilities, configuring auth, working with LLM prompts that accept user input, setting up deployment security, or assessing compliance. Also use when DAST findings need remediation.","https:\u002F\u002Fgithub.com\u002Fsandeep-mewara\u002Flifecycle-agent-orchestrator\u002Fblob\u002Fmain\u002Fplugins\u002Flifecycle-agent-orchestrator\u002Fskills\u002Fsecurity\u002FSKILL.md",[175,176,179],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":177,"categoryName":178,"taxonomyType":103,"taxonomyTypeDesc":104},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":101,"categoryName":102,"taxonomyType":103,"taxonomyTypeDesc":104},[109,181,182,183,184,185,186,187,188,189,190,89,191,37,146,192,142,193,194,195],"security standards","standards","vulnerability","remediation","dependency","owasp top 10","top","iam","logs","api","encryption","prompt injection","authentication","auth","pii"]