菜单
Initialization of an engineering-log task directory based on a template, including file creation, copying 04-execution-spec.md, and writing the original problem statement to 01-problem-statement.md.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | initializing-engineering-log-task |
| description | Initialization of an engineering-log task directory based on a template, including file creation, copying 04-execution-spec.md, and writing the original problem statement to 01-problem-statement.md. |
engineering-log/<yy>/<MM>/<NN>-<slug>.01-problem-statement.md../assets/04-execution-spec.md to 04-execution-spec.md.--slug, if directory naming needs to be controlled.Created task directory in engineering-log/<yy>/<MM>/.
The script prints the relative path of the created directory.
Created files:
chats/01-problem-formalization-chat-1.mdchats/02-solution-options-chat-1.mdchats/02-solution-hld-chat-1.mdchats/03-execution-spec-chat-1.mdchats/04-implementation-chat-1.md01-problem-statement.md02-solution-options.md03-solution-hld.md04-execution-spec.md01-problem-statement-formal.md is created later by the problem formalization step.
slug based on the problem statement.
The proposed slug must use ASCII letters, digits, and dashes only, should prefer English wording, and must be no longer than 60 characters.slug to the user.slug.NN within the month by scanning directories in engineering-log/<yy>/<MM>/.cat <<'EOF' | python3 ./processes/engineering-log/initializing-engineering-log-task/scripts/init_task_dir.py --dry-run
<paste problem statement here>
EOF
cat <<'EOF' | python3 ./processes/engineering-log/initializing-engineering-log-task/scripts/init_task_dir.py --slug <approved-slug>
<paste problem statement here>
EOF
cat <<'EOF' | python3 ./processes/engineering-log/initializing-engineering-log-task/scripts/init_task_dir.py --date 2026-02-07 --slug <approved-slug>
<paste problem statement here>
EOF
cat <<'EOF' | python3 ./processes/engineering-log/initializing-engineering-log-task/scripts/init_task_dir.py --yes
<paste problem statement here>
EOF
Export `transcript.md` + `brief.md` from the current chat as an evidence package for framework improvement, preserving user-authored request text verbatim and capturing the artifacts, decisions, friction, and execution evidence needed for postmortems.
Pre-flight git hygiene before commits and before reporting completion: resolve untracked task-created files (especially `*/src/**`), stage renames/moves, and verify that the staged set matches the intended commit scope.
Improve an AI agent framework from implementation evidence: analyze the model-produced result commit, human fix-up commits, and optional implementation chat evidence; then patch the correct framework artifacts and/or <project-local>/ so a rerun with the same prompt/model no longer needs the same manual fixes.
Improve the AI framework from design-stage evidence: analyze exported chat artifacts plus design documents such as the formal task statement, HLD, and execution spec; then patch the correct framework artifacts and/or <project-local>/ so similar future design chats require fewer clarifications, less rewriting, and produce more executable specs.
Synthesis of an operational description of a new or modified framework concept based on sources (books/articles/methodologies/industry): extract invariants, variants, and anti-patterns, then produce a Concept spec plus a separate 'Sources and Attributions' section to add or revise materials in `concepts/`.
Refactor Spring/JUnit HTTP tests to typed `*HttpApi` clients (controller-typed signatures, `*ForResponse`, optional `*ForError`/`*ForOutcome`, and JSON schema verification inside the client) when migrating away from direct WebTestClient/RestTestClient usage.