source-command-do-feature
starsforks
How to install source-command-do-feature?
pavel-molyanov/molyanov-ai-dev/source-command-do-feature
$npx -y skills add pavel-molyanov/molyanov-ai-dev --skill source-command-do-featureConverted Codex workflow from Claude slash command do-feature. Use when the user asks to run the equivalent command or describes this workflow.
SKILL.md
| 1 | <!-- Generated by sync-to-codex v1. Do not edit directly. --> |
| 2 | |
| 3 | # Command Workflow: do-feature |
| 4 | |
| 5 | Treat Claude-only tool names as conceptual workflow steps and use available Codex tools/policies. |
| 6 | |
| 7 | ## Codex Policy Gates |
| 8 | |
| 9 | - Ask before external actions such as GitHub repository creation, `git push`, deploys, or sending messages unless the user explicitly requested that exact action. |
| 10 | - Deployments must go through GitHub CI/CD; direct server access is only for emergency debugging of broken production. |
| 11 | - Never ask the user to paste secrets in chat. Direct them to `.env` files or GitHub Actions secrets. |
| 12 | |
| 13 | # Do Feature |
| 14 | |
| 15 | ## Project Documentation Autosync |
| 16 | |
| 17 | If this command changes any project-local `.claude/**` file, immediately run: |
| 18 | |
| 19 | ```bash |
| 20 | ~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply |
| 21 | ``` |
| 22 | |
| 23 | If sync reports a conflict, stop and report it. Include generated `.codex/**` changes in the same commit as the `.claude/**` source change. |
| 24 | |
| 25 | Execute a full feature using a team of agents. |
| 26 | |
| 27 | ## Step 1: Load Skill |
| 28 | |
| 29 | Invoke Skill tool: `Skill(skill: "feature-execution")` |
| 30 | |
| 31 | ## Step 2: Find Feature |
| 32 | |
| 33 | 1. User provides feature path or name |
| 34 | 2. Read `work/{feature}/tech-spec.md` — verify exists and approved |
| 35 | 3. Read `work/{feature}/tasks/` — verify task files exist |
| 36 | 4. If tech-spec or tasks missing → stop, tell user what's needed |
| 37 | |
| 38 | ## Step 3: Execute |
| 39 | |
| 40 | Follow the loaded feature-execution skill workflow. |
| 41 | The skill checks `checkpoint.yml` in Phase 1 and handles resume automatically. |
People who liked this also viewed
6 picksType
- hyperframes-cliUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, SkillsJul 2026
- request-refactor-planSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrSkillsMay 2026
- explore-codeRigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated braSkillsMay 2026
- ubiquitous-languageSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- scaffold-exercisesSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
