메뉴
Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | feature-dev |
| description | Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate. |
| allowed-tools | Read, Grep, Glob, Edit, Write, Bash, Skill, AskUserQuestion, mcp__codex__codex, mcp__codex__codex-reply |
/codex-test-review directly)❌ git add | git commit | git push — per @rules/git-workflow.md
This skill implements features but does not commit. /precommit is a quality gate only. To commit, the user must invoke /smart-commit --execute separately.
budget:token_budget200000</budget:token_budget>
Requirements → Design → Implement → Test + Review → Precommit Gate → Doc Sync
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
/codex- /codex- /verify /precommit /update-docs
architect implement /codex-test-review (or /precommit) /create-request --update
/codex-review-fast
| Phase | Command | Description |
|---|---|---|
| Design | /codex-architect | Get architecture advice |
| Implement | /codex-implement | Codex writes code |
| Test: Run | /verify | Run tests (lint → typecheck → unit → integration) |
| Test: Review | /codex-test-review | Mandatory — review test sufficiency (5 dimensions) |
| Test: Generate | /codex-test-gen | Generate unit tests for gaps |
| Test: Integration | /post-dev-test | Write missing integration/e2e tests |
| Review | /codex-review-fast | Code review (auto-loop) |
| Precommit | /precommit | lint + build + test (auto-loop canonical path) |
| Doc Sync | /update-docs | Sync docs with code |
| Doc Sync | /create-request --update | Update request progress |
| Refactor | /simplify | Final refactoring |
This is the core of feature-dev — ensuring sufficient test coverage before code review.
/verify → all tests pass?
Yes → Step 2
No → fix failures → re-run /verify
/codex-test-review → ✅ Tests sufficient?
Yes → Step 3
No → close gaps (Step 2a) → /codex-test-review --continue
| Gap Type | Remediation Command |
|---|---|
| Unit test missing/insufficient | /codex-test-gen → write tests → /verify |
| Integration/E2E missing | /post-dev-test → write tests → /verify |
/codex-review-fast → ✅ Ready?
Yes → Precommit Gate
No → fix issues → re-run /codex-review-fast (auto-loop)
If code changes after the latest ✅ Tests sufficient gate (e.g., fixes from code review), rerun /verify then /codex-test-review --continue before proceeding to precommit gate.
Follow @rules/testing.md for conventions (AAA, naming, evidence model).
Follow @rules/testing-project.md for project-specific overrides (directories, runner, adequacy mode).
| Change Type | Test Requirements |
|---|---|
| New Service/Provider | Must have corresponding unit test |
| Modify existing logic | Existing tests pass + new logic tested |
| Bug fix | Must add regression test |
| New API endpoint | Integration test required |
| Cross-service change | E2E test required |
Use project convention from @rules/testing-project.md. If no override is defined, follow ecosystem defaults:
| Source Pattern | Test Pattern |
|---|---|
src/<module>/ | test/unit/<module>/ or test/<module>/ |
scripts/<name>.sh | test/scripts/<name>.test.js |
skills/<name>/SKILL.md | test/skills/<name>.test.js |
/verify)/codex-test-review)/codex-review-fast ✅ Ready)/precommit ✅ All Pass)git add/commit/push executed⚠️ Auto-triggered by @rules/auto-loop.md — behavior-layer rule, not hook-enforced.
Only when change maps to a feature under docs/features/. Target detection uses 3-level fallback — see /update-docs for algorithm details.
precommit Pass
→ Locate feature docs (see /update-docs 3-level fallback)
→ /update-docs docs/features/<feature>/2-tech-spec.md
→ /create-request --update docs/features/<feature>/requests/<date>-<title>.md
→ /codex-review-doc (per updated file)
→ Safety valve: new code diff? → back to review loop (see /update-docs)
MUST re-review after fix until PASS (per @rules/auto-loop.md)
Review → Issues found → Fix → Re-review → ... → ✅ Pass → Next step
Input: Implement a fee calculation method
Action: /codex-architect → /codex-implement → /verify → /codex-test-review → /codex-review-fast → /precommit
Input: This code needs refactoring
Action: /simplify → /verify → /codex-test-review → /codex-review-fast → /precommit
Input: Feature dev, continue (resuming work)
Action: Check git status → identify remaining tasks → continue from current phase
First-principles UI/IA reasoning: turns a `<scenario>` + API field set into JTBD analysis, principle-anchored field-priority decisions, anti-pattern findings, and a bidirectional UI↔API gap report. Trigger: UI、UX、資訊架構、IA、scenario-driven UI、欄位優先級、information hierarchy. Not for: visual/CSS work (use `/frontend-design`), post-build critique (use `/critique`), or simplifying existing layouts (use `/distill`).
Necessity audit for over-designed spec elements. Use when: auditing lifecycle spec (1-requirements / 2-tech-spec / 3-architecture) for YAGNI/KISS violations, challenging necessity of FRs/NFRs/abstractions/configs via Codex adversarial debate. Not for: FP reasoning validity (use /codex-review-spec), completeness check (use /feature-completeness), detail review (use /codex-review-doc), or code-level simplification (use /simplify).
Sequential squash-merge of stacked PR chains into an epic branch. Handles dependency-ordered rebase, collision-safe backup tags, CI monitoring (delegates to /watch-ci), and post-merge verification. Use when: merging a chain of stacked PRs into an epic branch, collapsing a linear PR stack into per-PR squash commits, preparing an epic branch for final review. Triggers on: 'merge PRs into epic', 'squash chain', 'collapse PR stack', 'epic merge', or when user has a linear PR dependency chain (PR A -> B -> C) targeting an epic branch. Not for: single PR merge (use /create-pr + GitHub UI), simple rebase (use /smart-rebase), pre-merge analysis (use /merge-prep). Output: chain analysis table + backup tag manifest + per-iteration AskUserQuestion gate + verification log.
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
Post-development recap wrapper. Use when: AI/Codex just finished implementing a feature and the user wants a guided walkthrough with scope detection + doc generation + follow-up Q&A. Not for: generating only a doc (use /recap-doc), Q&A over an existing recap (use /recap-ask), technical share-out (use /tech-brief), first-principles reasoning of an existing doc (use /fp-brief), general code tracing (use /code-explore). Output: ScopeReport → briefing-recap-<date>.md → interactive Q&A session.
Interactive Q&A over an existing recap document. Use when: user wants to ask follow-up questions about a briefing-recap-<date>.md produced by /recap-doc, with recap-bounded context + out-of-scope redirect + optional promote-to-request. Not for: generating a new recap (use /recap-doc), general project Q&A (use /ask), code tracing (use /code-explore). Output: per-turn answer referencing file:line + end-of-session promote prompt.