Awsx Start Issue Planning Session
Productivityawsx-start-issue-planning-sessionAwsx Start Issue Planning Session is an Agent Skill for productivity published in the pulumi/pulumi-awsx repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Manual-only AWSX issue planning session starter. Use only when explicitly invoked to start a planning-only session for a GitHub issue or feature request, produce a planning brief, and stop before editing.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/pulumi/pulumi-awsx/blob/HEAD/.agents/skills/awsx-start-issue-planning-session/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/awsx-start-issue-planning-session, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
AWSX Start Issue Planning Session
This is a manual-only launcher skill. Use it only when the user explicitly invokes it. Its output is a planning brief, not code.
Inputs
Use the issue, PR, branch, or task details supplied with the invocation. If the target is missing, ask for it and stop.
Workflow
- Use
$awsx-issue-planningfirst. - Do not edit files, implement code, commit, or create a checked-in spec.
- Re-check live context as required by
$awsx-issue-planninginstead of trusting prior attempts. - Treat rollout summaries, memories, old worktree diffs, and abandoned PRs as historical attempts, not accepted design guidance.
- Use supporting AWSX skills only for planning evidence, following
$awsx-issue-planningrouting. - Produce the planning brief required by
$awsx-issue-planning. - Make the brief easy to carry into the implementation session. Prefer a concise, copyable brief in chat. If the user asks for a durable handoff, create or update the requested issue/PR comment, checked-in spec, or handoff file instead of inventing a location.
- Stop after the brief.
Brief Requirements
The brief must meet $awsx-issue-planning requirements, especially the
definition-of-done, service-requirements, and immediate-follow-up issue
sections.
Delegated approval is not permission. A prompt like "implement if the brief says
implementation should proceed" still delegates approval back to this same
session; follow $awsx-issue-planning and stop after the brief.