implement

Implement

Execute the implementation plan for a module, one feature at a time.

Pre-Implementation (every session)

1. Run read-context skill to orient
2. Read tasks from the active plan path (see skill.md Plan Paths convention)
3. Read progress.json to find current feature status
4. Read artifacts/05-implementation/{module}/task-{N}-{slug}.md if it exists for the target feature (previous session context)
5. If iterations enabled, also read the master plan path for broader module context if needed
6. Pick the highest-priority feature in "pending" status
7. Set up the module branch. Follow skill.md "Repos and Git":
   • Read the module's repos from the repos: front matter of artifacts/03-modules/{module}/module.md. If it lists no repos, follow "No repos listed" in skill.md "Repos and Git"
   • For each repo: if it has uncommitted changes, stop and ask the user what to do. Changes inside the haren folder do not count as uncommitted changes for this check
   • For each repo: if the branch feat/{module-slug} does not exist, create it from the repo's default_branch, or from the current branch if default_branch is not set. Then switch to it
   • Record branch and repos for the module in progress.json via update-tracking skill
   • If the module status is planned, set it to implementing via update-tracking skill

Implementation Loop

For each feature:

1. Update feature status to "in-progress" via update-tracking skill
2. Delegate to superpowers:subagent-driven-development:
   • Pass the full task description from tasks.md
   • Pass the design context from design.md
   • Ensure TDD discipline via superpowers:test-driven-development
3. After implementation:
   • (a) Commit the code in each repo that the feature changed: git -C <repo> commit with a descriptive message. In the monorepo layout, make one code commit for all repo keys; see skill.md "Repos and Git"
   • (b) Record each new commit SHA in progress.json lastCommit.<repoKey> via update-tracking skill
   • Update feature status to "evaluating" via update-tracking skill
   • Append to task session log (task-{N}-{slug}.md): what was done, decisions made, any deviations from plan, and the commit SHA for each repo
   • Emit "feature-ready" event to events/events.jsonl
   • (c) Commit the haren files (session log, progress.json and events/events.jsonl) in the haren repo. List the code commits in the message, for example docs(checkout): task 2 session log — backend@abc1234, frontend@def5678. In the monorepo layout the haren folder is in the same repo, so (a) and (c) are two commits on the same branch: the code commit first, then the haren commit. In the workspace layout, commit the haren files on the haren repo's current branch. Do not create a module branch in the haren repo.
   • Never push