AgentSkillsCN

forge-adjusting

Forge项目的架构师技能。在规划阶段（研究、POC、全面规划）进行识别，搭建DESIGN.md文件，生成features.json并附带验证脚本。具备交互性——在生成功能之前，可与用户就架构方案展开讨论。可通过“Forge规划”“规划功能”“生成功能”等指令触发。

SKILL.md
--- frontmatter
name: forge-adjusting
description: >
  Replan a forge project mid-execution. Use when the user wants to change the
  feature plan, add new features, modify scope, or adjust priorities after
  development has started. Handles POC failures and architecture pivots.
  Triggers: "forge adjust", "replan", "add features", "change plan".

Forge Adjusting

You are helping the user modify a forge project's plan mid-execution. Read existing state before proposing changes. Never break completed work.

Phase 1: Orientation

Read these files:

  • •features.json — current feature list with statuses
  • •forge.toml — scopes and principles
  • •context/ — decisions, gotchas, patterns, poc, references from completed work
  • •feedback/ — current test state, session reviews

Report to the user:

  • •Feature counts: done / in-progress / pending / blocked
  • •POC outcomes: which passed, which failed, which are pending
  • •Blocked features and their reasons
  • •Accumulated context summary (count per category)

Phase 2: POC failure handling

When context/poc/{id}.md has Result: fail:

  1. •Read the outcome — understand what failed and why
  2. •Identify features that depend on the failed POC (via depends_on)
  3. •Propose alternatives to the user:
    • •New POC with different technology/approach
    • •Reduce scope to avoid the problematic area
    • •Adjust architecture to work around the limitation
  4. •Update DESIGN.md unknowns:
    • •Mark failed POC as [!] with explanation
    • •Add new [ ] if proposing a new POC approach

Phase 3: Discuss changes with user

The user will describe what they want to change. Common scenarios:

  • •Add new features ("add pagination to search")
  • •Modify existing pending features
  • •Change priorities
  • •Add or modify scopes
  • •Respond to blocked features
  • •React to POC outcomes (pivot, proceed, or abandon)

Phase 4: Apply changes

Rules for modifying features.json:

  • •Never change done features — they're verified and committed
  • •Never remove done features — they may be dependencies
  • •Blocked features: can be unblocked, modified, or replaced
  • •Pending features: can be modified, reprioritized, or removed
  • •Claimed features: warn the user — an agent may be working on it
  • •New features: add with proper deps, verify commands, scope

Principle enforcement for new features:

  • •Every verify script includes cargo fmt --check and cargo clippy -- -D warnings (P3)
  • •Implementation verify scripts include specific tests that prove the deliverable (P2)
  • •POC verify scripts check for context/poc/{id}.md (P2)
  • •New scopes: add to forge.toml first, then reference in features

Phase 5: Validate

  • •All depends_on references point to valid feature IDs
  • •All scope values exist in forge.toml
  • •All verify scripts exist and are executable
  • •No circular dependencies
  • •DESIGN.md unknowns updated if POC pivot occurred
  • •Review the changes with the user before committing

Definition of Done: Updated features.json, verify scripts for new features, DESIGN.md unknowns updated if POC pivot.