基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/oyi77/1ai-skills --skill executing-plans命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Android and mobile application security testing — emulators, rooting, traffic interception, dynamic instrumentation. Use when testing mobile apps for vulnerabilities, reversing APKs, or bypassing security controls on Android.
Self-reflection + Self-criticism + Auto-learning from corrections + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when working with self improving.
Plan and execute a comprehensive red team engagement covering reconnaissance through post-exploitation using MITRE ATT&CK-aligned TTPs to evaluate an organization's detection and response capabilities. Use when working with conducting full scope red team engagement.
| name | executing-plans |
| description | Use when you have a completed, Momus-approved plan artifact ready for execution with checkpoint discipline |
| domain | development |
| author | oyi77 |
| license | Apache-2.0 |
| subdomain | software-development |
| tags | ["coding","executing","plans","software-engineering","testing"] |
| version | 1.0.0 |
persona: name: "Domain Expert" title: "Master of Executing Plans" expertise: ['Specialized Knowledge', 'Best Practices', 'Industry Standards'] philosophy: "Excellence through expertise." credentials: ['Industry leader', 'Practiced expert', 'Thought leader'] principles: ['Quality first', 'Continuous improvement', 'Evidence-based decisions', 'Customer focus']
Martin Fowler - Chief Scientist at ThoughtWorks, Software Architecture Expert
Load plan, review critically, execute tasks in batches, report for review between batches.
| Rationalization | Reality |
|---|---|
| "I'll figure it out as I go" | A structured approach saves time and reduces errors. Follow the workflow in this skill rather than improvising. |
| "I already know this topic" | Familiarity breeds shortcuts. Use the checklist to verify you haven't missed critical steps. |
| "This doesn't apply to my situation" | The patterns here generalize across contexts. Adapt, don't skip — the underlying principles hold. |
| "One more tool will fix it" | Adding complexity rarely solves process gaps. Master the core workflow first. |
Trigger phrases:
"executing plans"
"When you have a completed, Momus-approved plan ready for implementation"
"When following a structured plan with clear task breakdowns"
"When checkpoint reviews are needed between execution phases"
When you have a completed, Momus-approved plan ready for implementation
When following a structured plan with clear task breakdowns
When checkpoint reviews are needed between execution phases
When you need to execute multi-step implementation plans
Gate Check:
.sisyphus/plans/OKAYExecution Flow:
Core principle: Batch execution with checkpoints for architect review.
Canonical standard: agent-docs/plan-artifact-standard.md
Execution gate: no implementation execution before plan exists under .sisyphus/plans/ and Momus verdict is OKAY.
Announce at start: "I'm using the executing-plans skill to implement this plan."
.sisyphus/plans/Plan ID, Status, Momus Verdict, and Evidence PathOKAYDefault: First 3 tasks
For each task:
When batch complete:
Based on feedback:
After all tasks complete and verified:
STOP executing immediately when:
Ask for clarification rather than guessing.
Return to Review (Step 1) when:
Plan drift means execution reality no longer matches the approved plan.
When drift is detected:
.sisyphus/plans/.OKAY and evidence is updated.Don't force through blockers - stop and ask.
OKAYRequired workflow skills:
| Rationalization | Reality |
|---|---|
| "I'll do this later" | Explain why this excuse is wrong for this skill |
| "This is simple, skip steps" | Even simple tasks benefit from process |
After completing this skill, confirm:
# Example: TDD workflow
def test_user_creation():
user = create_user(name="Alice", email="alice@example.com")
assert user.name == "Alice"
assert user.email == "alice@example.com"
assert user.created_at is not None
def test_user_creation_invalid_email():
with pytest.raises(ValidationError):
create_user(name="Alice", email="invalid")