Feature implementation

Summary

Shows the implementation step — clearing agent context with /clear, then prompting the agent to implement all task groups from the feature spec. Emphasizes the developer’s role as architect/supervisor, observing progress and reviewing changes.

Key Takeaways

• Clear context before implementation: use /clear to give the agent a fresh start focused on the spec
• Implement in task groups: you can implement all groups at once or one at a time for smaller, safer steps
• Developer = architect/supervisor: your role shifts from writing code to reviewing and providing clear contracts

视频信息：Feature implementation

---

English Script

We’re working on the plan for the first feature in the project roadmap. We finished the feature spec. Let’s do the full implementation of this feature. Just to refresh ourselves, we do a quick review of this feature specs plan. This was the first feature, hello Hono. The feature spec documents have what we need. To start your implementation, you’ll want to clear out your context with a /clear command. Let’s go back to the agent and enter a prompt to implement all the task groups. Sometimes you might choose to do task groups one at a time for even smaller steps and commits. This technique is especially helpful for areas where small mistakes can compound later, like in security or database management.

While Claude is running, you can observe the changes it displays in the console to see its progress in real time. Afterwards, we can watch for the final changes in the commit window and visit the changes. This gives us an early jump on reviewing the work. This is the key role of the developer in such a paradigm, to act as an architect or supervisor and ensure that the agent is provided with a clear contract. We can also see the summary of what was done. As you can see, the agent provides extra details on the work performed for each of the task groups. Now, let’s go to the package.json file. And in there, let’s run the app. The server starts in the console. The browser shows the result of this feature spec. Not much. We said nano, but it’s a good feeling to see pixels on the screen. We just implemented a feature. The agent did its validation. In the next lesson, we’ll do ours.